As I was trying to install recovery on my tab, I think I screwed up big time.
After rooting following this guide(which worked) this is what happened when I tried to restart to recovery from the Rom Manager app (I stress : I didn't install the recovery from the Rom Manager, I know it's not the proper one) :
http://imgur.com/SBAb8
It's the screen I get when I launch the tab with the power button.
Worse : this is what I get when I power it on holiding the volume up button :
http://imgur.com/LqqFC
It's bad isn't it ? Any way to fix it ?
It won't power off.
Thanks...
Ive done this before. Can you not boot into download mode. I first started by leaving it to see if it would eventually restart on its own. If that doesn't work for you, while trying to turn it off hold down the volume down key. If I'm no mistaken this is how I managed to get mine back. Kind of forcing the restart in the direction you want it to go. Once there, I used fast boot to boot a known recovery, did a wipe but not sure if this was necessary, and then a restart, while holding thumbs. Hopefully you will have some luck with this as well.
Sent from my Nexus 7 using XDA Premium HD app
Well, I think Santa came by this night : when I woke up, the tab was working and almost fully charged...
Thanks !
Update : oh God, I'm an idiot ! You what that icon is ? It's the background of the recovery. It's just that it's not showing the usual list of actions by default. You need to press Power+Volume Down while on that screen to make it work !
However my problem is that I can't seem to flash another recovery (it's Android System Recovery <3e>) and that one doesn't allow any Rom to flash...I tried flashing the latest recovery with Odin and through fastboot : it does seem to work from the reports but when I try to access it, it's this this old recovery...
EDIT : Actually whenever I try to flash newer recoveries through Odin and Fastboot, I always end up having that old recovery instead...
EDIT : I dared it, I try installing the latest Recovery from the Rom Manager App (not the touch though) and it worked but I can't flash any rom due to a getprop error (assert failed : getprop ("ro.product.device") == "p3" || getprop ("ro.build.product") == "p3" E:Error in /sdcard/path to the rom I flash.zip (Status 7).
It may be because it's a recovery for the p4. But still it's the only recovery that will flash instead of that old recovery...
So I went back to stock 3.0 with Odin. I rooted it (through skitzandroid-recovery.img) and now I tried installing the latest recovery through fastboot and it still doesn't work.
Here's a capture of the Recovery and the attempt to flash a CM9 rom :
http://i.imgur.com/lsqSo.jpg
Any idea ?
DannyBiker said:
So I went back to stock 3.0 with Odin. I rooted it (through skitzandroid-recovery.img) and now I tried installing the latest recovery through fastboot and it still doesn't work.
Here's a capture of the Recovery and the attempt to flash a CM9 rom :
http://i.imgur.com/lsqSo.jpg
Any idea ?
Click to expand...
Click to collapse
Glad you came right with the fix, I haven't been able to flash a new recovery since the 3.2 update. Nothing works, I've tried fast boot flash, Odin and even ROM manager (I know, I thought why not, this tab is practically unbrickable ) which caused the issue you reported in this thread for me. Its a real hassle not having a working recovery. On all my other devices, I download an update, boot to recovery, and flash it. On the p7100 I have to take out my laptop, and boot into the recovery.
Very frustrating. But last week I got an early Christmas present, the nexus 7
so I will probably put a good stable cm9 on the p7100 ( thanks pershoot) and let my kids and wife carry on with what has been a very good tablet.
Sent from my Nexus 7 using XDA Premium HD app
But can you access a recovery in any way that allow flashing cm9 or cm10 ?
When it comes to recovery, rooting, etc, this tab is a piece of crap...
DannyBiker said:
As I was trying to install recovery on my tab, I think I screwed up big time.
After rooting following this guide(which worked) this is what happened when I tried to restart to recovery from the Rom Manager app (I stress : I didn't install the recovery from the Rom Manager, I know it's not the proper one) :
http://imgur.com/SBAb8
It's the screen I get when I launch the tab with the power button.
Worse : this is what I get when I power it on holiding the volume up button :
http://imgur.com/LqqFC
Click to expand...
Click to collapse
The first screen is the stock recovery in action, you need to wait for the timeout (5-10m) for the tablet to reboot itself to normal mode; rebooting through the power button wont work since it is locked into recovery boot (second screen).
DannyBiker said:
EDIT : Actually whenever I try to flash newer recoveries through Odin and Fastboot, I always end up having that old recovery instead...
EDIT : I dared it, I try installing the latest Recovery from the Rom Manager App (not the touch though) and it worked but I can't flash any rom due to a getprop error (assert failed : getprop ("ro.product.device") == "p3" || getprop ("ro.build.product") == "p3" E:Error in /sdcard/path to the rom I flash.zip (Status 7).
It may be because it's a recovery for the p4. But still it's the only recovery that will flash instead of that old recovery...
Click to expand...
Click to collapse
Either you flashed the wrong recovery or you used Rom Manager; Rom Manager has no proper 10.1v support, and will try to flash the p7500 recovery, which will work for most tasks; however, most CM-based ROMs have a pre-flash test which will be tripped up by the wrong recovery version, giving the error above.
You can flash the proper recovery through fastboot/Odim and then install the ROMs, but do not use Rom Manager afterwards, since it will detect a different recovery and try to flash the wrong one again.
I tried that and I still can't flash any working recovery. Odin or Fastboot, the flash goes fine but it just doesn't show...
So I make it worked by pure luck :
I tried flashing the .tar.md5 recovery with fastboot (instead of the .img one) which caused an error on boot. Something that said "unrecoverable bootloader error 0*00000" that scared the **** out of me.
However, Odin mode was still accessible. I flashed the tar.md5 through Odin and this time, it worked !
Thanks...
Related
I can't seem to get a ROM to install on my motodroid - I have the latest ROM Manager and the ClockworkMod recovery app flashed but every time I try to install a ROM (either downloaded w/ ROM Manager or via a file saved to the SD vai the USB cable) I get the attached alert display. Alt+Ctrl+Del reboots me back to the starting point...
What's wrong?
Tom
Having the same problem!
Having the same problem and getting the same screen after reboot.
i dnt think rom manager works on milestone/droid .. AOR is recommended ..
rrohanjs said:
i dnt think rom manager works on milestone/droid .. AOR is recommended ..
Click to expand...
Click to collapse
ROM Manager works on Droid, but not on Milestone.
?
I have a Droid, i am still having the same problem with rom manager. I used superoneclick to root, I have the latest busybox update, and superuser.
ashersgate said:
I have a Droid, i am still having the same problem with rom manager. I used superoneclick to root, I have the latest busybox update, and superuser.
Click to expand...
Click to collapse
I don't know if this works like it does on Milestone, but have you tried holding the camera button+volume up?
Try 4.....
Tried holding those no good. would like to get gingerbread on it soon. thks for the help so far.
Think I did push those button soon enough. 5th try it is installing.
ashersgate said:
Think I did push those button soon enough. 5th try it is installing.
Click to expand...
Click to collapse
So that key combo worked?
well.......
It brick the phone but i was able to recover from it. How can I get the apps on my sd card back on my phone.
seems like holding 'x' work to get me back from brick
I was able too restore back to the rpm i was using before i started with a backup in rom manager......awsome so now i can play without worry,,,,,, thanks so much!!!!!!
More on the problem
So, I consistently get the screen in the original post if I try to select the option presented after the download is complete to automatically boot to recovery and install the ROM - but if I install from a .zip while already in ClockworkMod, I am successful in installing a ROM. The problem seems to come with doing an over-the-air download in ROM Manager then attempting to transition to ClockworkMod to do the install. Alt-Ctrl-Del while on the screen displayed in the original post reboots and gets me back to my existing ROM...
It seems like something is not working as it should be, but it seems I have a way to make things work...
Tom
"Reboot into Recovery" also fails
I just tried to "Reboot into Recovery" from ROM Manager and that also failed (gave me the dead screen shown on the original post)...
Booting while holding x gets me into ClockworkMod successfully. I currently have ClockworkMod version 3.1.0.2 installed (it has given me the most success so far).
Any suggestions?
Tom
It seems I was wrong - I'm not currently able to boot into recovery using the x button during boot...
Tom
Getting better
I flashed back to the "current" ClockworkMod - 2.5.0.1 - and now I can "Reboot into Recovery"...
Maybe not better...
Errr My device seems flaky - I tried to install a ROM and the transition to ClockworkMod did not work again... Isn't this supposed to "Just work"?
More success yesterday
Once I got Pete's Gingerbread ROM loaded/installed (via .zip file) my problems getting to ClockworkMod and trying new ROMs seem to have cleaned up.
After performing the "e-mail connect" (to do that I had to turn off Droidwall) I was successful in downloading directly to the phone and flashing a new ROM.
Good luck all...
Tom
Hi everybody.
In the past I already flashed custom ROM to routers, so I thought I had the skill to undergo the path of flashing ROM to a phone.
Wrong.
I have countless tabs opened tried to solve my stucked phone, and my PC is running out of memory; and I'm running out of hope.
I own a S Plus GT-i9001.
I wanted to get rid of all the bloatware present in the phone, so I gained root privileges.
Like explained here. It worked perfectly.
Since deleting all the unnecessary apps didn't look working, I thought "well, it is a rainy day, you had this device for a while, why don't you flash some ROM?"
So,
1. I followed this guide, but, needless to say, Rom Manager was not fulfilling to its duty. Indeed I backuped everything I needed, but the stock rom
2. I followed then this guide, point 3, to install ClockworkMod Recovery directly. Before, everytime I tried to enter the recovery menu, I was bounced to the original recovery menu, because ROM manager did not succeed.
With this guide, I managed to boot into ClockworkMod Recovery.
I then started backing up the ROM to the external SD, and it seemed working.
It was popping out with a message "E:Can't mount /cache/recovery/command", but since all the operations went successful, I did not care much (fail, I suppose)
3. I tried to boot back into the phone, before installing the new ROM, just to double check I saved everything, and then the drama began. I was just continuously bounced back at CWM Recovery menu, no way to get in the phone.
I tried anyway to install the AOSP 4.0.4. and all the steps went successful, but still nothing, I would always reboot automatically into CWM Recovery.
4. I tried restore from backup in external SD, it ran successfully, but still couldn't load the phone
5. I then googled into the "E:Can't mount /cache/recovery/command" error, so I ended up somewhere that they were advising to flash FeaCore Phoenix Recovery tool. Indeed it did not display anymore such an error
6. I tried again with he AOSP 4.0.4 ROM, but it showed then the following error
Code:
assert failed: getprop("ro.product.device") == "thunderc" || getprop("ro.build.product") == "thunderc"
so I ended up here and changed the zip accordingly.
7. I also tried this instructions here to perform the most ultimate massive wiping.
8. I installed the AOSP 4.0.4, and the update-Gapps-ICS-20712.zip, it worked, no errors.
Still, it reboots into the recovery menu.
I can't get out of this damned recovery menu, it is crazy! I have used so many recovery tools in PCs, you usually are able to leave them, maybe not able to restore the OS, but you never get stuck into a circle of hell like this!
Please, does anyone has some advice for me? I don't want to waste a 6-months old device
thank you!
You should reflash CWM with odin like this then try flashing a rom again.
If that doesn't work flash a stock frimware through Odin also with the AriesVE.ops file active.
All guides tell you to put the "recovery-clockwork-5.5.0.4-ariesve.tar.md5" or the stock firmware file as "one package". Doing that results into large file errors or odin getting stuck on "downloading..."
Putting the file under phone got my phone back to life, after softbricking it by using CWM 6 thouch.
switchboy said:
You should reflash CWM with odin like this then try flashing a rom again.
If that doesn't work flash a stock frimware through Odin also with the AriesVE.ops file active.
All guides tell you to put the "recovery-clockwork-5.5.0.4-ariesve.tar.md5" or the stock firmware file as "one package". Doing that results into large file errors or odin getting stuck on "downloading..."
Putting the file under phone got my phone back to life, after softbricking it by using CWM 6 thouch.
Click to expand...
Click to collapse
man, you saved my life!
you and the powerful, mighty Odin, god of the Valhalla!
oh, it feels so awesome!
but since I never learn (that was enough of a message to tell me to stop messing around)...
how do I install the ROM I'd like, go through the same process (my phone is now as as when I bought it) or can I use somehow Odin?
jv_guano said:
man, you saved my life!
you and the powerful, mighty Odin, god of the Valhalla!
oh, it feels so awesome!
but since I never learn (that was enough of a message to tell me to stop messing around)...
how do I install the ROM I'd like, go through the same process (my phone is now as as when I bought it) or can I use somehow Odin?
Click to expand...
Click to collapse
I realised that, since I flashed the recovery-clockwork-5.5.0.4-ariesve.tar you provided, if I would boot in recovery mode, it would be still there.
and it is.
but still it is showing the error
E:Can't mount /cache/recovery/command and, needless to say, it is not loading the ROM correctly, it stucked again
I don't get which part am I doing wrong!
jv_guano said:
I realised that, since I flashed the recovery-clockwork-5.5.0.4-ariesve.tar you provided, if I would boot in recovery mode, it would be still there.
and it is.
but still it is showing the error
E:Can't mount /cache/recovery/command and, needless to say, it is not loading the ROM correctly, it stucked again
I don't get which part am I doing wrong!
Click to expand...
Click to collapse
Well, I sorted it out (absolutely, in a mysterious way!!! )
I downloaded the recovery-clockwork-6.0.1.2-ancora.tar.md5 from here, and I followed again your instructions for flashing it with Odino (rigorously NOT ticking one package).
When rebooted, I had the AOSP 4.0.4 Stock, shiny and sparkling!
without even entering the recovery menu and reinstalling!
but I guess I will need to do a clean install again, now that seems that CWM 6 is digested by my phone
Hello!
I have a Samsung Galaxy S Captivate previously rooted over a year ago. I was mostly using CyanogenMod for a while, and some time ago, I decided to try out some random ROM (can't remember the name, but it was an unofficial port of ICS).
It had some issues and bugs, so I decided to switch back to CyanogenMod. I've tried installing CyanogenMod 7.2, 9.0 and 10.0
Everytime, I get the following error message:
Code:
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "captivate" ||
getprop.("ro.build.product") || ... (and so on)
E:Error in /sdcard/#whateverpackage#.zip
Status 7
Installation aborted.
*Where "whateverpackage" is the zip/ROM I am trying to install.
Things I attempted to no avail:
1. Toggling asserts. I get the same error.
2. Reflashing recovery-clockwork-2.5.1.2, but I get the same type of error.
3. Installed USB Drivers for Samsung, and attempted to run Odin3 One-Click Downloader (I897UCJF6-final-OCD-REV0.exe), but it isn't responding it seems.
I'm thinking of trying to install ADB and see if I can get the device to properly go into "download mode" and see if Odin responds.
This may be important: When I boot in recovery, the top of my screen shows "CWM-based Recovery v5.5.0.2"
So if anyone knows a straightforward fix to this, or can at least give me rough steps to try/follow, I would greatly appreciate your help.
Thanks for taking the time to read this!
You could have quickly found an answer if you searched "status 7" or "assert failed." It simply means your phone is identifying as a different device because of the ROM you flashed. You can get around this by flashing a kernel appropriate for whatever you're trying to install, so Devil or Semaphore will do. From there, reboot recovery and install the ROM.
korockinout13 said:
You could have quickly found an answer if you searched "status 7" or "assert failed." It simply means your phone is identifying as a different device because of the ROM you flashed. You can get around this by flashing a kernel appropriate for whatever you're trying to install, so Devil or Semaphore will do. From there, reboot recovery and install the ROM.
Click to expand...
Click to collapse
I did look up assert failed, but I couldn't get a clear answer.
I didn't occur to me to look up "status 7"; just seemed like a very cryptic error code.
Thank you for your advice nonetheless. I'll update if the error persists.
Semaphore & CyanogenMod
So, I flashed Semaphore 2.8.0 and then attempted to install CyanogenMod 10 (Android 4.1.2, I think).
Got Status 0.
Tried reflashing Semaphore 2.8.0, and 1.2.6. No progress.
Any recommendations?
I tried to flash CyanogenMod 9 on Semaphore 1.2.6 and got Status 7.
Thanks.
Headless_One said:
So, I flashed Semaphore 2.8.0 and then attempted to install CyanogenMod 10 (Android 4.1.2, I think).
Got Status 0.
Tried reflashing Semaphore 2.8.0, and 1.2.6. No progress.
Any recommendations?
I tried to flash CyanogenMod 9 on Semaphore 1.2.6 and got Status 7.
Thanks.
Click to expand...
Click to collapse
If you would read a bit before doing the flashing you would know that status 0 is from rebuilding the partition. You simply need to flash CM10.1 twice. So it goes like this: Flash CM10.1, reboot recovery, flash CM10.1.
BWolf56 said:
If you would read a bit before doing the flashing you would know that status 0 is from rebuilding the partition. You simply need to flash CM10.1 twice. So it goes like this: Flash CM10.1, reboot recovery, flash CM10.1.
Click to expand...
Click to collapse
I do look up the error. Just no one actually mentioning that until your post.
Thank you for your advice.
I flashed it 3 times (rebooting each time) and I always get Status 0.
More explicitly:
Code:
-- Installing: /sdcard/cm-10.0.0-captivatemtd.zip
Finding update package...
Opening update package...
Installing update...
E:Error in /sdcard/cm-10.0.0-captivatemtd.zip
(Status 0)
Installation aborted.
Side note: I'm on Semaphore 2.8.0 and I used Heimdell to flash it (through Ubuntu).
Any additional thoughts?
Headless_One said:
I do look up the error. Just no one actually mentioning that until your post.
Thank you for your advice.
I flashed it 3 times (rebooting each time) and I always get Status 0.
More explicitly:
Code:
-- Installing: /sdcard/cm-10.0.0-captivatemtd.zip
Finding update package...
Opening update package...
Installing update...
E:Error in /sdcard/cm-10.0.0-captivatemtd.zip
(Status 0)
Installation aborted.
Side note: I'm on Semaphore 2.8.0 and I used Heimdell to flash it (through Ubuntu).
Any additional thoughts?
Click to expand...
Click to collapse
Tried simply booting up?
If that doesn't work, reflash without rebooting recovery.
BWolf56 said:
Tried simply booting up?
If that doesn't work, reflash without rebooting recovery.
Click to expand...
Click to collapse
I tried rebooting the device, but, after shortly showing "At&t", it goes straight to the Recovery screen.
I tried installing CM10 again, but same error.
Just reflashed Semaphore. It always gets stuck on At&t after flashing (for several minutes). Is that normal?
So I've been removing the battery, and putting it back in. Then it goes straight to 'Semaphore CWM Recovery v6.0.2.0'.
My steps from there:
Attempted to install CM10. Status 0 error. Turned phone off.
Rebooted straight to CWM-Based Recovery v6.0.1.5.
Tried installing CM10 from there. Status 0 error.
Rebooted. Right back to Recovery v6.0.1.5.
Tried installing CM10 again. Status 0 error
Tried installing CM9. Phone rebooted midway and got stuck on 'At&t' screen.
Rebooted using 3-key button combo (to get to recovery screen).
Went to Recovery v6.0.1.1. (What the hell is going on?)
Tried installing CM9. SUCCESSFUL. Also installed gapps for ICS while at it.
Booted to CM9 correctly.
Rebooted to Recovery and it was still Recovery v6.0.1.1.
Rebooted back to CM9 properly.
Edit:
Rebooted to Recovery. Updated to CM10.
Noticed that Recovery version changed back to v6.0.1.5.
CM10 seems to be working properly.
Anyone knows why I am getting 3 different Recovery versions?
Note: Sorry for the somewhat long post. I just figured I should tell you everything I am doing step-by-step.
Headless_One said:
I tried rebooting the device, but, after shortly showing "At&t", it goes straight to the Recovery screen.
I tried installing CM10 again, but same error.
Just reflashed Semaphore. It always gets stuck on At&t after flashing (for several minutes). Is that normal?
So I've been removing the battery, and putting it back in. Then it goes straight to 'Semaphore CWM Recovery v6.0.2.0'.
My steps from there:
Attempted to install CM10. Status 0 error. Turned phone off.
Rebooted straight to CWM-Based Recovery v6.0.1.5.
Tried installing CM10 from there. Status 0 error.
Rebooted. Right back to Recovery v6.0.1.5.
Tried installing CM10 again. Status 0 error
Tried installing CM9. Phone rebooted midway and got stuck on 'At&t' screen.
Rebooted using 3-key button combo (to get to recovery screen).
Went to Recovery v6.0.1.1. (What the hell is going on?)
Tried installing CM9. SUCCESSFUL. Also installed gapps for ICS while at it.
Booted to CM9 correctly.
Rebooted to Recovery and it was still Recovery v6.0.1.1.
Rebooted back to CM9 properly.
Anyone knows why I am getting 3 different Recovery versions?
Note: Sorry for the somewhat long post. I just figured I should tell you everything I am doing step-by-step.
Click to expand...
Click to collapse
Actually that's great details, thanks!
Have you tried flashing CM10 from CM9? It will still have to rebuild the partition so 2 flashes will be needed.
BWolf56 said:
Actually that's great details, thanks!
Have you tried flashing CM10 from CM9? It will still have to rebuild the partition so 2 flashes will be needed.
Click to expand...
Click to collapse
Yes sir, I just did that. It works
Thanks for your help.
Just wanted to thank you both for this thread. Totally helped me upgrade my Cappy to CM10.1 today. Thanks!
Hi!
Today i wanted to update my firmware just because Samsung Kies asked me if i wanted to. I couldn't have been more wrong when i chose to update.
The update froze at 3% and after a lot of time i unplugged the phone and ended up with a brick instead of a phone.
If i try to turn it on, i get a black screen with a "phone--!--pc" picture. I can enter Download Mode by pressing VolumeDown + HomeButton + PowerButton and i get an android logo with ''Downloading... Do not turn off target'' written under it.
My phone was never rooted, nor updated ( it remained with its out-of-the-factory OS and everything ).
For the past 6 hours i've been trying to use Odin v4.43 along with AriesVE.ops (the one from the well-known WORKED2 archive) to try and get recovery-clockwork to work.
So my questions are:
Given the fact that my phone was not rooted, how can i get my GT-I9001 to work again? Is this even possible?
Can i first root it in its condition, then flash a custom rom like cyanogenmod? Or do i need to install a stock rom and then try a custom one?
What other options do i have?
Everything i've tried so far with Odin froze while downloading and i have no other solution to this problem. Please help!
zerkylo said:
Hi!
Today i wanted to update my firmware just because Samsung Kies asked me if i wanted to. I couldn't have been more wrong when i chose to update.
The update froze at 3% and after a lot of time i unplugged the phone and ended up with a brick instead of a phone.
If i try to turn it on, i get a black screen with a "phone--!--pc" picture. I can enter Download Mode by pressing VolumeDown + HomeButton + PowerButton and i get an android logo with ''Downloading... Do not turn off target'' written under it.
My phone was never rooted, nor updated ( it remained with its out-of-the-factory OS and everything ).
For the past 6 hours i've been trying to use Odin v4.43 along with AriesVE.ops (the one from the well-known WORKED2 archive) to try and get recovery-clockwork to work.
So my questions are:
Given the fact that my phone was not rooted, how can i get my GT-I9001 to work again? Is this even possible?
Can i first root it in its condition, then flash a custom rom like cyanogenmod? Or do i need to install a stock rom and then try a custom one?
What other options do i have?
Everything i've tried so far with Odin froze while downloading and i have no other solution to this problem. Please help!
Click to expand...
Click to collapse
Yes it is possible as long as your device boots into Download mode.
No you can't root it in its current condition.
You need to download a stock firmware, flash it using Odin or Heimdall (recommended), then root it and finally install a custom ROM if you want.
kalpetros said:
Yes it is possible as long as your device boots into Download mode.
No you can't root it in its current condition.
You need to download a stock firmware, flash it using Odin or Heimdall (recommended), then root it and finally install a custom ROM if you want.
Click to expand...
Click to collapse
Thank you for answering!
I fixed the issue. Tried different usb port along with a different version of CWM (5.5.0.4) which I installed with Odin v4.43. CWM 5.5.0.4 caused a bootloop, but i used it only to install CWM 6.0.4.9 from external_sd, so the bootloop problem was gone. Then flashed CyanogenMod 11 and now works like a charm !
I attached an archive with CWM 5.5.0.4, AriesVE.ops and Odin v4.43, so that anyone having my problem can solve it the way i did. But keep in mind that this version of CWM *may* cause a bootloop, so prior to installing it, you should have a working version of CWM on your external_sd. Use CWM 5.5.0.4 to install the better version of CWM from your external_sd. Also, whatever you do is at your own risk!
the galaxy tab 8.9 is quite aged so i thought that i could pump some newer juice in it. bad luck, it got bricked. stuck at the samsung logo, bootlooping over n over
it started when i tried to install twrp, my current recovery is cwm. currently, i can only boot into download mode. so, i tried flashing back cwm, twrp and even stock recovery but all of it failed. i also tried flashing another stock rom but it also failed. odin didnt even tried, it stucked at "SetupConnection"
can anyone hand out a helping hand?
when i tried to reboot it back now, it asks me to "select recovery from kies" something like that about an error.
?*
bumayang said:
the galaxy tab 8.9 is quite aged so i thought that i could pump some newer juice in it. bad luck, it got bricked. stuck at the samsung logo, bootlooping over n over
it started when i tried to install twrp, my current recovery is cwm. currently, i can only boot into download mode. so, i tried flashing back cwm, twrp and even stock recovery but all of it failed. i also tried flashing another stock rom but it also failed. odin didnt even tried, it stucked at "SetupConnection"
can anyone hand out a helping hand?
Click to expand...
Click to collapse
I have a similar problem. I am waiting for tablet to die (battery dead) then plug into wall charger and it should bring up download mode.
Do you have the LTE model?
droiduzr2 said:
I have a similar problem. I am waiting for tablet to die (battery dead) then plug into wall charger and it should bring up download mode.
Do you have the LTE model?
Click to expand...
Click to collapse
im afraid i dont
Going to necro this because I've had the same problem as the OP (but not 2nd message).
I had CWM 5, tried to flash TWRP (so I could get Nougat), ended up with no recovery bootable. Can anyone help me get back with a recovery?
Tried to flash TWRP 3 but stuck at "failed". The tab was stuck in like 2% status, and wouldn't respond to Odin commands to flash again, so I had to reboot it.
Then there was no recovery I could boot into (icon would just flash when I tried to enter recovery from bootloader menu).
If I don't try to boot into bootloader menu, it sometimes would show the message "Software update failed", but would still accept Odin flashing.
I tried flashing via odin TWRP 2.6, 2.7, 3.0, CWM 5.5, Stock recovery and all did not work. TWRP <=2.7 and CWM would flash OK but still could not enter it, icon would just flash the icon but not change screen.
It doesn't display "Software update failed" screen anymore, but when I try to boot it normally with power button, it will always go into bootloader mode. If I restart with power + vol -, it would go into bootloader menu for you to choose between recovery and bootloader mode.
What should I do next to get a recovery back?
I haven't tried from Odin flashing a full stock image since I can't find a working download link anymore since hotfiles and devhost are down. Does anyone have a .tar or .tar.md5 for Odin flashing they could link me?
Never mind. I managed to find a stock image flashable by odin, flashed that and recovered stock recovery (and a stock ROM). I used the stock recovery to flash TWRP and then used TWRP to flash a new ROM, and all seems to be well now!
pd12 said:
I used the stock recovery to flash TWRP and then used TWRP to flash a new ROM, and all seems to be well now!
Click to expand...
Click to collapse
It is not possible with Stock recovery to flash the TWRP Recovery.
I think your Stock image has an CWM Recovery ( its a modified Stock Recovery ) and it is possible to flash TWRP.
pd12 said:
I managed to find a stock image flashable by odin, flashed that and recovered stock recovery (and a stock ROM).
Click to expand...
Click to collapse
Hi, that's great news! Would you be able to share where you got the ROM from and what version of Odin you used (and where you got it) please?
I am stuck on the boot screen with my GT-P7300. The stock images I have found so far don't flash through Odin and also fail in the recovery.
Many thanks in advance
dertobes