Hi,
Summary: Was running Cyanogenmod 10.2.0 and tried to update to 10.2.1. Phone won't boot. Using CWM recovery 6.0.4.3. Factory Reset reports that it can't mount / clear /data (due to encryption?). Can get phone into CWM recovery and Download mode. Haven't been able to successfully connect to PC (ADB or Odin) even though I have samsung drivers.
I do have an unencrypted SD card in the phone so my normal way of flashing is to connect SD card to PC, download, then in CWM recovery to install ZIP from SD card.
Looking to get into any good state - Cyanogenmod 10.2.1, or 10.2.0, or heck go back to stock.
**** I think the answer might be use ODIN and flash back to stock, I see some guides but haven't been able to get ODIN to "see" my phone *****
Details
I had downloaded Cyanogenmod update to phone using "About this phone" menu and when I tried to "Install it" from that window the machine booted into recovery, immediately failed, and rebooted. The phone is encrypted (work requires this) and I discovered Cyanogenmod saves the download to encrypted phone storage and CWM recovery doesn't support encryption.
Downloaded 10.2.1 to my SD card and flashed it. (no back-up, no wiping of cache). Installed successfully, reboot asked me for my encryption password, Android optimized apps, rebooted, encryption password, then blue spinner spins forever.
From here I started my troubleshooting:
- I flashed back to 10.2.0 then flashed Gapps again, no change.
- Reading about boot.img I installed ADB and SDK Manager and tried connecting and flashing boot.img. ADB devices shows up empty. I have installed Samsung drivers.
- Researching going back to Stock points me to installed Triangle to reset my custom ROM count - but I can't boot.
Thanks in advance.
Matt
[Solved] This is for anyone who happens to read this wondering if their phone is screwed. Relax! If you can get into Download mode and Odin can see your phone, you'll be o.k.
Turns out the machine and cable you use do matter. I tried for days connecting using my MAC running Windows 7 Virtual Machine. Once I switched to my Win7 laptop and used the original Samsung cable things starting working out more smoothly.
Steps:
1) Get Odin (mine was 3.09) and run as admin. If you see an error in Korean it's because you have to unzip the entire Odin folder.
2) Get stock firmware for t-mobile. There's only 1 firmware file, I didn't need a PIT nor a specific recovery step. The t-mobile firmware includes everything I needed. Flashing failed in Odin saying Complete Write failure. This had me stumped for hours and hours. When I switched to stock cable and Win7 laptop it succeeded. I never had to check Nand erase all or repartitian (almost did in desparation though). Flash took about 10 minutes but eventually PASSED.
3) However, when it rebooted it asked for encryption key and my old one didn't work. Turns out their are more steps. This scared me.
4) Reboot into recovery (up, home, power) which gave a bunch of scary error messages. Actually those listed at the bottom in http://forum.xda-developers.com/showthread.php?t=1840030.
5) Factory Reset then Wipe Cache
6) Reboot
Now I'm back at stock and breathing a sigh of relief. Unclear if I'll ROM back to Cyanogenmod.
I spent hours and hours reading discussions and going down one dead end after another. I'd say it was like looking for a needle in a haystack but it was the complete opposite. It was like looking for a specific needle in a sea of needles. Every search query yielding tantilizing results and a plethora of step by step guides that ultimately didn't work. A very frustrating experience all around. Good luck to anyone who reads this.
Hi Matt
Similar thing happened to me last night. I am/was using Omni-Nightly build. I plugged it in to the charger before bed, and it rebooted, saying upon reboot - "Encryption Failed" and saying the only way to recover would be to wipe the machine and start again, it then rebooted and all I get is the Samsung boot screen.
Tried rebooting, wiping, everything, Odin, Android Toolkit, nothing works. It shows up on my Linux PCs but not accessible, but not windows at all.
Hi there,
I just updated P8000 via OTA update and after downloading the Update, the phone restarted and stops at the elephone boot Logo (about 30 min )!!
I did 5 Restarts but every time it hangs at the boot logo...
In the past i did no other updates or flashing ROMS.. nothing!
When i press "Volume Up" and "Power" to Start, i get three Options:
Recovery Mode
Fastboot Mode
Normal Boot
Using Recovery Mode leads to: Symbol Android Robot with "No Order" (in german : "Kein Befehl")
Using Fastboot Mode leads to: Nothing (Recovery Menue stays)
Using Normal Boot leads to: restart and hanging at Elephone Boot Logo
So, I am running out of Options... any ideas?
Cheers, Albert
Same. I tried using the official instructions to flash the stock rom but the SP flash tool stops responding after download button is pressed
a.cid said:
Same. I tried using the official instructions to flash the stock rom but the SP flash tool stops responding after download button is pressed
Click to expand...
Click to collapse
The Hardware of P8000 is pretty cool, but the Software is "§$§"%§""!$%
When you go to recovery mode and get the the android robot symbol. Press again Vol up + Power until you enter to recovery. Make a 3 wipe (data factory , cache and dalvink). Reboot and uninstall the El loader. Use another Loader instead of El Loader
i had the same problem. (in English NO COMMAND) I only flash Eragon ROM again. Sometimes you have to repeate.
AL 6677 - ELEPHONE MUST BE TURN-OFF !!!!!!! and CONNECT USB CABLE REPEATEDLY !!!
After that everything goes according to instructions
https://translate.google.at/transla...-p8000-rooten-und-flashen/&edit-text=&act=url
same problem since OTA my phone is bricked and cant unbrick
neonero said:
When you go to recovery mode and get the the android robot symbol. Press again Vol up + Power until you enter to recovery. Make a 3 wipe (data factory , cache and dalvink). Reboot and uninstall the El loader. Use another Loader instead of El Loader
Click to expand...
Click to collapse
THX a lot, I found only the 2 Options to wipe data factory and cache....... dalvink was not displayed in the menue (screenshot attached)
How to uninstall the EL Loader ?
showshow747 said:
i had the same problem. (in English NO COMMAND) I only flash Eragon ROM again. Sometimes you have to repeate.
AL 6677 - ELEPHONE MUST BE TURN-OFF !!!!!!! and CONNECT USB CABLE REPEATEDLY !!!
After that everything goes according to instructions
THX, I will try to flash Eragon, CM 12.1 is still not available, isn't it?
Click to expand...
Click to collapse
No CM 12.1 is not available yet.
In order to uninstall EI Loader, install first root (superSU), then install ccleaner and you can uninstall EI Loader (In system app)
Hi there, sorry for the revival !
But i got the same problem: OTA update, fail, P8000 blocked on boot screen.
I tried wipe data/factory reset + wipe cache -> nothing changed, still boot screen blocked...
Then, i tried to use flash tool, but, the phone isn't booting, so my pc isn't recognizing the phone..
I'm not even sure that I correctly installed the drivers..
Can i use flash tool even if the phone is blocked to boot screen?
I downloaded this ROM: stock-rom-elephone-p8000-20150907-android-5-1 (this is my first post i can't post URL..)
Because i got some issues with my phone and support told me to try it.
But when i follow the tutorial, launching "donwload" and connecting the phone, nothing happening..
The phone turn on, and display recharging logo, and flash tool still wainting.
Recovery mode -> "No command", Volume up + power is working, i used it to wipe datas
But at the moment, i'm still blocked, since 2 days, i dont know what to do
Can someone help me?
Thank you by advance, i hope my english isn't so bad
Zywoon said:
Hi there, sorry for the revival !
But i got the same problem: OTA update, fail, P8000 blocked on boot screen.
I tried wipe data/factory reset + wipe cache -> nothing changed, still boot screen blocked...
Then, i tried to use flash tool, but, the phone isn't booting, so my pc isn't recognizing the phone..
I'm not even sure that I correctly installed the drivers..
Can i use flash tool even if the phone is blocked to boot screen?
I downloaded this ROM: stock-rom-elephone-p8000-20150907-android-5-1 (this is my first post i can't post URL..)
Because i got some issues with my phone and support told me to try it.
But when i follow the tutorial, launching "donwload" and connecting the phone, nothing happening..
The phone turn on, and display recharging logo, and flash tool still wainting.
Recovery mode -> "No command", Volume up + power is working, i used it to wipe datas
But at the moment, i'm still blocked, since 2 days, i dont know what to do
Can someone help me?
Thank you by advance, i hope my english isn't so bad
Click to expand...
Click to collapse
Yes you can use SPFlash tool evenif the phone stucks in the boot screen. Simply switch the phone off, start SPFlash tool and then connect the phone to usb.
If you follow the instructions from elephone, then your phone should working again: http://bbs.elephone.hk/thread-1037-1-1.html#.VofQ13wvdpo
Cheers
Hi, and thx for the help.
The driver is correctly installed now, i had to allow unsigned drivers in windows parameters.
So, i followed the tutorial, again.
I configured SP flash tool, clicked download, and then connected powered off P8000 with USB.
But, again, the phone displays recharging logo, and flash tool still waiting...
The phone is recharging so the USB is working, so i don't know how to make my PC detect the phone......
Is there a way or a thing that i missed?
thank you..
EDIT: i finally got a timeout error from flashtool..
I missed something, but what !? i can't remove P8000 battery, is there somthing to do to get it detected by windows?
Like a boot mode, or a magic formula... i'm open
For MTK Driver installation:
Did you follow skeletons Guide? http://forum.xda-developers.com/elephone-p8000/help/guide-windows-10-mtk-vcom-usb-drivers-t3264884
I'm sorry to say, that I do not have any experience with windows installation, this problem, because SPFlash tool performes on my 64bit Linux very well, without any driver trouble.
Cheers
Hi,
I'm on windows 8.
I used SP_driver_v2.0, that is an .exe
it's the only driver tips gived in most of tutorial
I allowed unsigned drivers installation, and i correctly installed it.
I tried too use flashtool before and after restarting the PC-> no changes
Flashtool doesnt detect the phone
I start getting crazy..
I have repaired mine, so i'll share
Al6677 said:
Hi there,
I just updated P8000 via OTA update and after downloading the Update, the phone restarted and stops at the elephone boot Logo (about 30 min )!!
I did 5 Restarts but every time it hangs at the boot logo...
In the past i did no other updates or flashing ROMS.. nothing!
When i press "Volume Up" and "Power" to Start, i get three Options:
Recovery Mode
Fastboot Mode
Normal Boot
Using Recovery Mode leads to: Symbol Android Robot with "No Order" (in german : "Kein Befehl")
Using Fastboot Mode leads to: Nothing (Recovery Menue stays)
Using Normal Boot leads to: restart and hanging at Elephone Boot Logo
So, I am running out of Options... any ideas?
Cheers, Albert
Click to expand...
Click to collapse
So the simple way to solve it is flashing the latest stock elephone p8000 ROM, which you can find on google easly
1. as described on other forums, you have to install the adnroid drivers, then get the sp flash tool, and have an un-zipped stock elephone p8000 ROM.
2. if you are stuck at bootloop, do the following to power off the phone so you can flash the ROM
1. Long press power button until power off
2.Do it fast--Press volume Up and then hold power button
3. choose recovery (volume up choose menu, volume down enter)
4. android logo with red triangle is displayed( "no command")
5. hold power button and press volume up
You're in recovery mode
3. select power off
4. open the SP flash tool >go to download tab>opne "scatter loading"( you will find it in the Folder where you unzipped the stock elephone p8000 ROM, if you have more folders there, chose "firmware" folder)
5. on the left side, under scatter loading, you will find a "pull-down" tab - it will be written "download" chose "firmware upgrade" or "upgrade"
6. start the process, then connect your elephone p8000 (it must be powere off) via usb cable to the PC, the process will start,and in less then 5 Minutes you have a factory new Elephone p8000 with the latest good update
7. WATCH OUT- it will erase all your data, absolutely all your data on the phone, except SIM and SD card.
Hope it helped, if not, feel free to ask me =)
Hello,
I have similar problem. Bought P8000 5 days ago. Did update today. Bricked. Stuck at logo ... I tried to flash but SP flush tool but the process isn't starting. When I downloaded ROM I received long list as on the screenshot: kaczorowscy.name/Screenshot.png
I have ubuntu - I see lsusb and dmesg see the phone (it is shut down from recovery menu) but maybe I am missing something ....
Ok here is what id did:
1. Get SP flashtool
2. get newest stock ROM
3. Shut down phone through android recovery menu (start phone with holding volume up, select recovery mode, wait for dead android, hold volume up and unblock button for 3 sec.)
4. Open SP flashtool - use "format all + download" of ROM (unzip and select scatter file from rom) - click start
5. Connect shut downed phone
6. Dot OK! from flashtool
PS. Flashing removed IMEIs - they are both written on the battery - you need to use android service menu to check them with special codes and reboot the phone.
Thanks ALL! :good:
Fix - Recovery Mode
Al6677 said:
Hi there,
I just updated P8000 via OTA update and after downloading the Update, the phone restarted and stops at the elephone boot Logo (about 30 min )!!
I did 5 Restarts but every time it hangs at the boot logo...
In the past i did no other updates or flashing ROMS.. nothing!
When i press "Volume Up" and "Power" to Start, i get three Options:
Recovery Mode
Fastboot Mode
Normal Boot
Using Recovery Mode leads to: Symbol Android Robot with "No Order" (in german : "Kein Befehl")
Using Fastboot Mode leads to: Nothing (Recovery Menue stays)
Using Normal Boot leads to: restart and hanging at Elephone Boot Logo
So, I am running out of Options... any ideas?
Cheers, Albert
Click to expand...
Click to collapse
When I was trying to root my p8000 I couldn't flash a custom recovery, fortunately I discovered that to access recovery on stock android you need to go to the screen with the android and "no command"/"no order" text and hold down Vol+Up and Power for 3~ seconds and then release power, this will boot you into recovery mode, If wiping cache/factory reset isn't enough "fastboot flash recovery <image>.img" SHOULD work now
hope this helped
Hey guys long time lurker here !
I'm experiencing an issue with my G4 h815 currently with AICP (rev from around April) and TWRP (from around January 2017).
Since the last update of AICP I did (so back in April) everything went fine with the phone.
I did nothing weird with the phone (haven't installed an app for months, neither droped the phone or whatsoever)
It suddenly froze while I was browsing Chrome, then bootlooped 2 times, couldn't get past the "swipe to unlock" thingy.
I then decided to get into recovery mode with PWR+Volume down buttons => "do you want to erase blabla ?" => YES => "Are you sure blabla" => YES.
The "TeamWin" logo from TWRP appeared once, phone bootlooped again, and until then it just freezes after the second "YES" when I try to get to recovery mode and then bootloops again.
Obviously this crap happens when I'm far away from home (and for a long time) so I installed drivers / ADB stuff on my laptop but I can't get the phone to be recognized by win 10 in any way. ADB says : error: device '(null)' not found
I'm a bit lost right now, any thoughts / keywords that could help me getting sorted are welcome !
Many thanks in advance,
Fosco
Ok I managed to go a bit further ... discovered about the download mode thingy (Vol UP while plugin it to computer).
I installed LG UP, picked a KDZ file here.
I was then able to "upgrade" the phone with the stock rom : Complete success from the process perspective. It then froze on the basic LG logo. I removed the battery, entered recovery mode, reset worked, phone went back alive => "android is preparing apps, etc" but then it rebooted and froze again on LG logo.
Am I missing something ?
EDIT : Tried LG Bridge method aswell ... can't get it to go further than boot ... still freezing on the boot screen
Went ahead, disassembled the phone and heated the CPU ... looks like it needed it-ish.
I am still stuck on the LG logo, but atleast now I have the green android guy having his belly "moving stuff" and the blue led is glowing :laugh:
Nah seriously this is getting annoying ... IDK what to do next ... Cure it with lawnmower ?
Hi guys,
my wiley fox swift gets stuck in a continual optimising apps cycle. I can't enter recovery mode, when i press power+volume up it enters fastboot
(only see the black fastboot screen can't do anything). I did not change anything on my phone (not rooted) it worked fine yesterday and today i can't get it to work.
It's always optimising apps, if it's finished then i see the cyanogen logo and it starts optimising again shortly after.
I removed the battery and did wait about 15 minutes before putting it back in, i tried waiting (after 2 hours+ of it optimising i gave up),
i does not get recognised when i connect it to the pc (although i only used it to put stuff on the sd-card before) maybe a driver would fix this but i'm not sure which one.
I'm pretty clueless right now and i would be happy if someone can help me.
Saw the same thing on a friend's device today, used fastboot to factory reset the device. Insert USB in a powered-off device while holding vol+ then using fastboot do a "fastboot -w" to factory reset and recreate the (probably corrupted) data partitions.
i installed the minimal adb and fastboot connected my phone with my pc started it and tried it.
it doesn't recognize my phone and is stuck "waiting for any devices".
what can i do now? i'm not very experienced with android phones and fastboot.
dajohre said:
i installed the minimal adb and fastboot connected my phone with my pc started it and tried it.
it doesn't recognize my phone and is stuck "waiting for any devices".
what can i do now? i'm not very experienced with android phones and fastboot.
Click to expand...
Click to collapse
ADB needs debugging to be enabled in developer options
FASTBOOT will only work if the phone is in bootloader mode
I already said in my first post:
dajohre said:
I can't enter recovery mode, when i press power+volume up it enters fastboot
(only see the black fastboot screen can't do anything). I did not change anything on my phone (not rooted)
Click to expand...
Click to collapse
since i never changed anything in my phone I haven't enabled debugging in developer options, if I could access the bootloader mode I could reset my phone but like i said,
it enters fastboot and not the bootloader from which i could enter recovery mode
under these circumstances, can i do anything?
see here https://wiki.lineageos.org/devices/crackling/
Note they call bootloader mode Download
Ok i can access recovery mode now (it was explained wrong here)
i tried to factory reset but the problem still persits.
in recovery mode i did go to ->Wipe data/factory reset then i had the options (No/No/Yes -- delete all User data/No)
i choose the third option and it did load a short while. after a reboot it still wants to optimise apps.
what's the best option now? i can choose (Apply update\ Wipe data/factory reset\Wipe cache partition\wipe media\reboot to bootloader\View recovery logs)
Fix
Hi,
I had the same issue and wrote the Wileyfox customer support.
They provided me the following instructions to fix the issue:
Download:
* 1 - ZNH0EAS2NH
* 2 - ZNH2KAS7EB
* 3 - TOS111B
Repeat for File X in [1, 2,3] :
* Goto Recovery
* Update your phone using File X
Since this is my first post I am not allowed to post links.
Find the full document including file links here: h t t p s : / / we . tl / B1IpUP6wtB
Already after running the first update my phone booted again.
Only thing I noticed is that the UI feels a little laggy / slower than before.
Regards
Hello,
my wife got a S21 FE (SM-G990B/DS VD2). Yesterday it started to reboot over and over out of a sudden, showing the samsung logo first, followed by the knox logo, then shutting off and on again. Tried several guides to enter Recovery or Download Mode. The only thing that worked was entering download mode by pressing Vol up, down and power while a USB-Cable is plugged in, but as soon as i press the vol up button to pass the "warning screen", it shows some phone specs for a couple of seconds, shuts off and starts bootlooping again. After some hours, the phone once entered recovery mode when it lied next to me for about an hour. Tried to wipe cache, but just got an error I can't remember right now. Hoped it fixed itself when it made it to recovery and just rebooted to see if it works again, but then it just keept bootlooping again.
Since then I couldn't figure out why it once booted to recovery on it's own nor why I can't force it to enter recovery by pressing vol up + on.
Still hope it's just a faulty update or bug, but feels very much like it's a hardware related issue. Replacing the phone won't be an issue, but I'd really want to save data on the phone as my wife didn't make any backups and really wants to keep the photos.
As I just found guides that included recovery or DL-Mode, which are both no valid options for my case, I'd be thankful for any ideas to fix the phone or at least gain access to files before replacing it.
So.. did anyone come across similar issues and found a solution to revive the phone or are there any "unpopular" ways to recover samsung phones out of this state?
Edit:
Turned off completely overnight, booted once to system, looped again and now it's working like nothing ever happened. Got no clue what caused it or why it is working again. Saved everything for the case it happens again.
Wouldn't trust that device anymore, but my wife wants to keep it.
¯\_(ツ)_/¯
I would just like to reply here and add my own potential fix and also would like confirmation that it would work.
So I have a SM-G996B in a boot loop which returns a 'fs_mgr_mount_all' error. Possible to reboot into recovery mode, cleared cache and restarted bootloader etc with the same boot loop. Powered off and connected to PC for Download mode for ODIN recovery but upon pressing volume up, it then restarts again so Download mode recovery is impossible.
I know however that Developer options and USB debugging was enabled on the device as well as unlocked boot loader. I was able to download the correct original stock OS based on the PDA , CSC and Android version.
I have then installed the latest ADB software on my PC and Samsung USB drivers.
By then rebooting into recovery mode, I have the option of 'Apply update from ADB'. I have then confirmed the device connects using the ADB devices command.
I would like to clarify one thing however. I want to keep the user data at all costs. By using the stock firmware and renaming as update.zip, will it use the HOME_CSC and not the CSC file? If not would it work if I open the zip and remove the CSC before re-zipping to make sure?
Thanks
Reebee said:
Hello,
my wife got a S21 FE (SM-G990B/DS VD2). Yesterday it started to reboot over and over out of a sudden, showing the samsung logo first, followed by the knox logo, then shutting off and on again. Tried several guides to enter Recovery or Download Mode. The only thing that worked was entering download mode by pressing Vol up, down and power while a USB-Cable is plugged in, but as soon as i press the vol up button to pass the "warning screen", it shows some phone specs for a couple of seconds, shuts off and starts bootlooping again. After some hours, the phone once entered recovery mode when it lied next to me for about an hour. Tried to wipe cache, but just got an error I can't remember right now. Hoped it fixed itself when it made it to recovery and just rebooted to see if it works again, but then it just keept bootlooping again.
Since then I couldn't figure out why it once booted to recovery on it's own nor why I can't force it to enter recovery by pressing vol up + on.
Still hope it's just a faulty update or bug, but feels very much like it's a hardware related issue. Replacing the phone won't be an issue, but I'd really want to save data on the phone as my wife didn't make any backups and really wants to keep the photos.
As I just found guides that included recovery or DL-Mode, which are both no valid options for my case, I'd be thankful for any ideas to fix the phone or at least gain access to files before replacing it.
So.. did anyone come across similar issues and found a solution to revive the phone or are there any "unpopular" ways to recover samsung phones out of this state?
Edit:
Turned off completely overnight, booted once to system, looped again and now it's working like nothing ever happened. Got no clue what caused it or why it is working again. Saved everything for the case it happens again.
Wouldn't trust that device anymore, but my wife wants to keep it.
¯\_(ツ)_/¯
Click to expand...
Click to collapse
Similar issue with same phone. In a bootloop after trying to root. None of the button combinations have worked for me, for the past several days.
Tried powering the phone off for the whole night.
When connected to the PC shows phone is in recovery mode via adb (blank screen though).
Want to know how to get into DL-mode, guaranteed.
Got to DL mode by pressing vol up + down + power + usb cable connected in PC and phone. However, couldn't do anything there, but maybe you can
Also, phone is still working and I still have no clue what was the problem and what fixed it.