Hello.
I am writing here as i am hoping that one of You experienced android users will be able to help me to fix my phone (i8150).
I am rather new to android and so far i have been following instructions very carefully and it wasn't the very first time i was flashing rom.
I did rooted my phone, flashed CWM Recovery via adb, used titanium backup, root explorer etc. Also its been long time since i started using Kezra V4 rom with ICS theme, unmodified vold.fstb. I never ever had any issues with the phone or rom.
To make things as clear as possible i will start with the brief info on what i did to my phone last week.
Last weekend (a week ago) i did a fresh install of Kezra v4 rom with ics theme, original vold.fstab, root explorer and launcher pro (placed in system/app).
Flashing process went fine, no errors in CWM (and yes i did wipe dalvik, cache, formatted system). Several apps were restored with titanium. Phone and rom were working as intended, no signs of slowdowns, errors etc.
Couple days latter i decided to add 1 ringtone and 1 notification sound. Both are ogg files and were placed to system/media/audio/ringtones and notifications. I did remember to mount as r/w change permissions and remount it as r/o. I rebooted phone once but i didn't see new ringtone or notification sound on the list so i rebooted it again. After second reboot the phone booted without any problems but once the system was loaded touch screen stopped to respond and the phone froze. I rebooted it again and this time everything went back to normal.
Yesterday i tried to copy new Kezra rom to my INTERNAL sdcar in order to flash it with CWM. But instead of that i stumbled upon a problem that is beyond my knowledge and comprehension. I DID NOT FLASH ANYTHING AT THIS POINT AS I LOST ACCESS TO CWM
- CWM Recovery disappeared - when i am trying to boot to CWM my phone turns off. There is very very very quick flash of the screen showing recovery but that is it.
- when copying 270mb rom to INTERNAL sdcard it stops at 10% with message that the file can not be read
- when copying smaller files, files are being copied from pc to phone but once the phone (usb storage) is disconnected from pc the files that were copied to internal sdcard are not there as if they were never copied
- i can copy files from external sdcard to internal sdcard with rootexplorer but after rebooting phone the files are gone from internal sdcard
- i can install any app from market or from sdcard but after rebooting, the installed app is gone, it doesnt exist in data/app, the cache files on internal sdcard are gone as well and the installed app is not on the list
- i can take pictures and if they are saved to internal sdcard they vanish after rebooting phone
- if i change any settings of the phone (volume, brightness, wifi settings, any settings) after rebooting phone the settings that i changed are reverted to the state from before rebooting
- i did try to delete those 2 files - ringtone and notification sound from the system/media/audio/ringtones and notification but after rebooting the phone they are still there not deleted (i do remember abot mounting r/w r/o and permissions)
- after formatting internal usb storage (settings/storage/format usb) and rebooting phone all the files are there - as if it was not formatted at all
- after formatting internal usb storage from pc and rebooting phone all the files are there - as if it was not formatted at all
- after "factory reset data" and rebooting phone nothing has changed as if it has not been reseted
- i tried to update superuser binary (my binary is 3.0.3) via wifi - there is new ver 3.0.3.2(ok), update(ok), downloading(ok),
gaining root(ok),remounting /system as rw (ok), md5sum(ok), changing file mode to 06755(ok), moving su (ok), checking md5sum(ok),
remounting /system as ro(ok), installed ver 3.0.3, update failed - superuser message -> "this updater cannot update the su binary on phones that have some kind of write protection on the system partition like S-ON"
Now i guess you are wondering if the phone works. Yes it does.
- it is eu phone bought in England and used in England
- the phone is not assigned to a network carrier, it is not locked in any way - network lock (off), network subset lock (off), SP lock (off), CP lock (off)
- I can make/receive calls and messages
- wifi, g3, tethering, bluetooth, gps, camera etc. are working fine
- all the applications including new apps are working fine as long as i don't reboot phone.
- I don't experience any slowdowns, crashes or freezes
- I have access to system files via root explorer, the phone is rooted
- i don't get any messages that file system is write protected
- rumdump works
- download mode works
Here is what i tried so far:
- flash CWM Recovery via adb but after rebooting i still have no access to recovery (no errors in adb - process completed)
- flash original stock recovery via adb but after rebooting i still have no access to recovery (no errors in adb - process completed)
- flash CWM Recovery via ODIN but after reboot i can not boot to CWM
- flash stock rom I8150XXKK1 via ODIN - no changes to rom. Phone is loadin the old rom
ODIN Explanation:
In both cases of flashin CWM and stock rom i followed the procedure step by step with and without automatic reboot. ODIN says that flashing is done and PASS. During automatic reboot phone doesnt reboot it only turns off. After manual reboot phone is loading old rom (Kezra V4 installed a week ago) and there is no sign of CWM.
So now i am wondering:
- is it software or hardware issue
- how can i identify and isolate the problem
- how to make the phone to save the changes after reboot
- how to get a working CWM Recovery so i can flash the phone
- How to make ODIN to flash the phone
What do You make out this?
Man.....I am so sorry.
I have never seen such a well documented OP...
Congrats on that first!!
I really am at a loss as to what to suggest, as you have covered so many bases yourself.
Just to me, looking again at your post, I don't really think those .ogg files have anything to do with it.
It seems your problems originated with flashing the Kezra Custom ROM.
To lose your Recovery Partition must mean some data corruption introduced by the flashing process.
I know you have flashed stock with ODIN, this was One Package??
I am not sure, but I think there may be Stock ROM which has seperate files.......???
It is just a suggestion, perhaps someone else may know.....
At least this will bump your post!!!
All I can say further is best of luck....hope it can be solved.
Also, there also is return for repair to Sammy.....as we say in Ireland.... Play the eejit!!
Sent from my SGW GT-I8150 using Tapatalk!!
Thanks Irish for taking your time to reply.
Well... yes i did my best to make the post as much descriptive as possible due to the nature of the issue itself.
When it comes to ODIN it was one file only. I didn't try with multiple files.
I don't think that ogg files itself are the source of all that mess. On the other hand i wouldn't blame Kezra rom.
As you noticed i tried to track down the time and place when it happend and how it all started.
It may be a coincidence but i suspect that "ogg glitch" (keep in mind that was the very first fail reboot and system crash of my phony since i bought it) has something to do with it. Why? All the settings, apps etc. in the phone are as they were set on Wednesday 28.03 including Alarm set to 8:00am. Same day "ogg glitch" occurred. Betwene Wednesday and Now no flashing has been done except all the mentioned steps (failed) that i have taken in order to restore my phone. Every time i reboot the phone, all the setting, apps etc. are being reverted to the state from before "ogg glitch"
Another thing is the message given by superuser while trying to update su binary. "Some kind of write protection like S-ON". (at this point i didn't have time to do a in depth search on "S-ON")
Now... i am not an expert but it makes me wonder... is it?
- internal phone memory (the chip itself) is corrupted or damaged
- the file system of internal memory is corupted
- system partition is corupted
- there is an issue with root access and permissions
- while copying ogg files to /system/... i made a mistake at some point and set wrong mount rw/ro and wrong permissions
- is such thing as "recovery loop" possible - after every each reboot the phone is "restored" to the state from before "ogg glitch"
When it comes to return to Samsung... The phone is not only working but is rooted, has a custom rom... She is not a VIRGIN mate.
Sorry, I didn't mean to say that Kezra's ROM is at fault......phew...nearly got into trouble there.
I meant that during the flash of the ROM, there may have been an event, loss of power??? which has caused corruption of the Partition system on your phone??
I know there is no locked Bootloader on our phone, which is what s-on indicates....usually HTC phones have/had this....hence problems with flashing Custom ROM's Recovery......
Somehow, your phone has got into a state which mimics locked bootloader, has to be corruption, IMO.
If you can locate ODIN files to flash separately, maybe will work, but I'm not sure..
As for returning to Samsung......
there is a thread here somewhere, Rio Saputro, where Sammy has accepted phones with boot-loops back for repair, due to hardware issues, so I am not sure haw much checking they do!!!
I can still access download mode but i think i wont be able to flash anything.
ODIN MODE
PRODUCT NAME: GTI8150
CUSTOM BINARY DOWNLOAD: NO
CURRENT KERNEL: UNKNOWN !!
Irish would You be so kind and compare that info with your downlod mode please?
Otherwise i think i will have to return my W to Samsung.
Cheers
jbs.sc said:
I can still access download mode but i think i wont be able to flash anything.
ODIN MODE
PRODUCT NAME: GTI8150
CUSTOM BINARY DOWNLOAD: NO
CURRENT KERNEL: UNKNOWN !!
Irish would You be so kind and compare that info with your downlod mode please?
Otherwise i think i will have to return my W to Samsung.
Cheers
Click to expand...
Click to collapse
Don't worry, your phone is not bricked.. Just download the Asian firmware from the development thread (it will have multiple files inside the package) and flash it through Odin (look for flashing process for multiple file package), you will be good to go.
Sent from my Novo704FC-E2 using Tapatalk
I have already tried multi part asian firmware provided by THE-E.
Same thing as with one file firmware.
With auto reboot phone just turns off and doesn't turn on.
Without auto reboot... well it just stays on and that's it.
After manual reboot i am back to the old rom.
I am using odin 4.43
Should i try other versions?
I do have factory gurantee on my phone till 2013 and if they won't accept it...
oh well s*** happens... not for the first nor the last time in my life. There is no fun of modding without a risk.
jbs.sc said:
I can still access download mode but i think i wont be able to flash anything.
ODIN MODE
PRODUCT NAME: GTI8150
CUSTOM BINARY DOWNLOAD: NO
CURRENT KERNEL: UNKNOWN !!
Irish would You be so kind and compare that info with your downlod mode please?
Otherwise i think i will have to return my W to Samsung.
Cheers
Click to expand...
Click to collapse
Hi friend.....
Not sure what your current state of play is, but my download mode was exactly as you have quoted above.
see this from last Christmas,
when I was in despair.....symptoms very similar to what you have now, after failed ODIN flash....I had no recovery and my phone would not boot, just download mode, as you have above.
However, I solved it pretty easily, after modifying my ODIN settings.
Unfortunately THE-E's instructions said "unmark Auto Reboot"......which is not correct.....
this meant the Flash never completed.......
See here for my celebratory post, much relieved...
This was very much like your recent experience.
I think there may be some hope/help for you there!!!!
Let me know......bast of luck......
Irish,
I did try with auto reboot marked. When ODIN starts the procedure of auto reboot the phone turns off but it doesn't turn on. ODIN waits for the phone till the flashing is completed and says PASS but the phone stays turned off anyway.
Btw. Perhaps i should use KIES to try to update and brick my phone.
I would have a valid reason to claim warranty
jbs.sc said:
Irish,
I did try with auto reboot marked. When ODIN starts the procedure of auto reboot the phone turns off but it doesn't turn on. ODIN waits for the phone till the flashing is completed and says PASS but the phone stays turned off anyway.
Btw. Perhaps i should use KIES to try to update and brick my phone.
I would have a valid reason to claim warranty
Click to expand...
Click to collapse
OK.....I think that was my last shot......I am out of ideas!!!
Maybe post screen shot of ODIN procedure if you can??
I can't remember how my phone reacted after PASS and Reboot, but that doesn't sound right.......
Can you post the ODIN Message output.....just so ppl can compare and perhaps help.
OK i tried to flash it again just to take screenshots. And again same thing.
OK.....just have a look at my thread here.......
which is a pdf of the Service manual I "procured"
There is something there about ODIN, which Samsung use as well....
I just noticed a little thing when using multiple files.....
they have also set the " Reset Time = 300" for their Flash.......
P.21....or [6 Level 1 Repair]........
the pdf files are a little out of sequence!!!!
Also, try flash without SD or SIM card inserted.....
Irish,
Just to let you know. I did what you suggested.
Flashing with timer, without sim card and without external memory did't help.
As far as i remember someone had similar problem, unfortunately solution was never found.
I think when it comes to ODIN i run out of options.
Thanks for all the help and assistance.
OK......out of suggestions here!!
It is just such a pity.....
download mode normally means "no brick-can flash"
Sorry we could not fix.....next move?? Sammy??
Best of luck anyway!!
Sent from my SGW GT-I8150 using Tapatalk!!
Did you try to flash only boot img? Not sure if that's possible but it looks like your boot is messed up.
Sent from my GT-I8150 using Tapatalk 2 Beta-5
I dont think it makes any difference what am i flashing.
Whether it is software or hardware problem it prevents phone from auto rebooting (and applying any changes made during flashing process)
Not only during ODIN auto reboot but also from download mode reboot (once in download mode you can press volume down button to reboot phone)
Just thinking if you try to do it part by part and not whole firmware in 1 go. But if you manage reflash image boot hope you should by fine
Related
Hi everybody,
sorry for bothering you, but I think I might need some help.
I tried to flash ParanoidAndroid (first try ever to flash a smartphone) but failed 'somehow'.
Initial steps to create the problem
Initial Status: Gingerbread on a Galaxy W; Pretty old and pretty messed up
Download the update.zip to root the smartphone => Becoming root worked!
Download ParanoidAndroid
Download Clockwork Recovery
Created backups using Titanium Backup as root.
Copied ParanoidAndroid to the GalaxyWs internal sd card (yes, this was my mistake)
Wipe cach partition => It said, it worked, I don't know if it did
Rebooted phone => all fine
Rebooted into recovery mode applied update from SD-Card=> Selected ParanoidAndroid.zip => ErrorMessage (I think it was something like file corrupt, sorry I'm not sure about the specific words, but it sounded like this is no updatefile or this file is not a valid zip file.
Status of the problem
Bootup shows Samsung Logo
Bootup than shows GalaxyW-Screen Logo
Bootup than shows the android recovery symbol OR directly reboots
When trying to open the recovery menu, every second time I get the message "Updating (...) Installing MultiCSC... Can't access /system/csc/DBT/system"
If opening recovery menu works, I can only acces the internal storage of the galaxy to install an update (tried the paranoidandroid several times, it doesn't work)
When plugging in the galaxy w to my USB port, I don't get an USB storage shown on my 2 laptops (1 "Windows 7", 1 "Ubuntu 14.0?" )
neither odin (4.43) nor Heimdall are able to flash any files.
So, simple question, what can I do next?
-I cannot copy clockworkmod to my smartphone
-I don't know if I can easily overwrite the kernel or the bootloader.
I searched the forum but didn't find a clear solution, so sorry if this special configuration was already asked.
Thanks for your help and best regards
FrankyDroid
FrankyDroid said:
[*]Rebooted into recovery mode applied update from SD-Card=> Selected ParanoidAndroid.zip => ErrorMessage (I think it was something like file corrupt, sorry I'm not sure about the specific words, but it sounded like this is no updatefile or this file is not a valid zip file.
Click to expand...
Click to collapse
Your ROM's download has been cut either by a connection issue or by you, That is why I always have a backup rom in my SD Card. Also For kitkat, make sure you got CWM 6.0.4.5 or higher. Personally i use PhilZ Touch Recovery. It is simple enough for me. And odin recognizes your phone only in download mode. So make sure you go to download mode then plug the phone in. And also make sure while working with odin, unplug all USBs and other phones
Hey MayB4ck,
thank you for the tips, I finally got it running Using Philz Touch Recovery. Works like hell
Best regards
FrankyDroid
My wife's SG3 SGH-I747 will show the white "Samsung" logo, then the white Samsung Galaxy S3 logo, then it goes black. Pulled the battery several times, no luck. I'm assuming this was caused by a failed update.
I can get it into download mode, I have cleared the Cache and rebooted with no luck.
I'm not a complete rookie at this, but I haven't done it for years and I'm afraid of losing the data on the phone.
How would you suggest I proceed to save the data? (Pictures and movies)
install a previous stock rom via the download mode? Or odin? I don't have a custom recovery installed.
Will the unbrick method work in my situation? If so will it wipe the phone?
I've searched the forum and can't find anyone saying if the data is salvageable.
I know it's my fault for not backing up her data, but she's in tears over losing pictures of the kids. Please help if you can.
Thanks,
Installing a ROM via Odin may require you to do a factory reset before it boots.
Boot into download mode and look at the screen. Do you see anything about a warranty bit?
I just get the download screen. (See attached picture) Nothing about a warranty
Options are:
Reboot system now
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
Then it shows:
#MANUAL MODE#
--APPLLYING MULTI-CSC...
APPLIED THE CSC-CODE : ATT
SUCCESSFULLY APPLIED MULTI-csc.
.
That is the recovery mode, not download mode. To get into download, press the home button, volume down, and power button. Once the phone starts to boot, release the power button and hold the other two until you see the download message and press volume up to continue.
You were right. In download mode it says:
ODIN MODE
product name: sgh-i747
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
QUALCOMM SECUREBOOT: ENABLE
WARRANTY BIT: 1
BOOTLOADER AP SWREV: 3
DOWNLOADING....
DO NOT TURN OFF TARGET!!
Since the warranty bit is 1, this tells me you have at least a 4.3 bootloader on your phone.
The only thing I can think of to get the files would be to flash twrp onto your phone in download mode. Then mount the drive, connect the phone to your computer, and use Windows Explorer (assuming you're on a Win machine) to copy the files off the phone.
audit13 said:
Since the warranty bit is 1, this tells me you have at least a 4.3 bootloader on your phone.
The only thing I can think of to get the files would be to flash twrp onto your phone in download mode. Then mount the drive, connect the phone to your computer, and use Windows Explorer (assuming you're on a Win machine) to copy the files off the phone.
Click to expand...
Click to collapse
Flashing a new rom would wipe the phone?
The last full firmware AT&T released was 4.1.1. The AT&T 4.3 and 4.4.2 ROMs were only released as OTA updates for an existing stock ROM and stock recovery on a phone.
If you want to flash a 4.3 or 4.4.2 ROM, you need to use a version found on XDA to to this. Trying to flash a 4.3 ROM onto a 4.4.2 bootloader and modem could brick your phone. In fact, any flashing procedure can result in a brick or a loss of user data.
Even if you successfully flash a ROM, the ROM may not boot without wiping the cache and all user data first.
Good to know, Thanks a BUNCH for the help.
You are awesome!
Now...let's pray this works!
If you install a custom recovery, you can create a backup of the existing ROM even if the ROM doesn't boot.
Cool,
Odin 3.07 sees the phone, i downloaded openrecovery-twrp-2.6.3.0-d2att.tar. Is it is loaded through the pda option?
Thanks again for your help.
Yes, flash it via the PDA section. Do not check anything except F.Reset time.
Flash TWRP, when you see the word Reset in the status windows, remove the USB cable, remove the battery, replace the battery, boot into recovery, create a backup of the rom, preferably to an external SD card. When the backup is complete, attach phone to computer, mount the partitions, locate files on the phone you want to save.
Done with install, backing up to SD now.
Ok, TWRP worked, I was able to safe the files (THANK YOU!!!). I used the file manager to find and copy the files to the sd card, then did a full backup. It never did mount to the computer, even after the drivers were installed.
It saved the backup with the file name: 1970-01-01--00-18-57 KOT49H.I747UCUFNJ1 so I'm guessing that is the build number it was trying to update to (KOT49H.I747UCUFNJ1). I can get to recovery mode and download mode, how should I go about making this phone work again?
I'm not sure how to check what version of bootloader I have. You scared me about the "bricking it" warning about flashing the wrong rom with the wrong bootloader.
If your are sure you saved the necessary files in two different places, boot into recovery and wipe cache , dalvik, and reboot. If it still won't boot, wipe cache, dalvik, and data in recovery, reboot.
Another option may be to use adb to pull files from the phone, you can even pull entire directories. I will work from recovery mode. There are tutorials on installing the toolkit for adb w/o installing all of the platform development tools. I use Linux so I can not verify how to do this on Windows, but it looks as simple as it was for me. Once adb is present on the PC, boot the phone into recovery, and in a command prompt window enter the command
Code:
adb shell pull /path/to/picture/directory C:\path\to where\you\want\it
and example may be
Code:
adb shell pull /sdcard/DCIM/camera C:\recoveredphotos
Check that I did my Windows path correctly
Hoping someone here can give me some help. Sometime last night my phone crashed - had an error message on the screen asking me if i wanted to restart - basically the android version of a blue screen.
I rebooted and when it started up it tried to activate but failed. Tried it a few times, never activated. I called sprint and they had me type in 2 different codes:
##72786# which didn't get an error but didn't help anything
They had me try a 2nd 6 digit number, which I'm not sure if it's unique to my phone or not so I wont post it here but that did nothing at all - typed in the ##______# and nothing happened. They claimed it was because the phone is rooted, but the phone is ONLY rooted. I haven't installed a new OS it's the stock rom as far as i can tell.
Anyone have any ideas whats going wrong here or how to fix it?
thanks
edit: and apparently now I wiped the OS from the phone since it wont go past the LG logo. Is there some way for me to either copy a rom onto the phone from TWRP or copy a backup onto the phone? I've got a couple of TWRP backups saved on my pc, but since the phone wont start up I don't have any way of copying them onto the phone - damn non-user removable sd cards.
merkk said:
Hoping someone here can give me some help. Sometime last night my phone crashed - had an error message on the screen asking me if i wanted to restart - basically the android version of a blue screen.
I rebooted and when it started up it tried to activate but failed. Tried it a few times, never activated. I called sprint and they had me type in 2 different codes:
##72786# which didn't get an error but didn't help anything
They had me try a 2nd 6 digit number, which I'm not sure if it's unique to my phone or not so I wont post it here but that did nothing at all - typed in the ##______# and nothing happened. They claimed it was because the phone is rooted, but the phone is ONLY rooted. I haven't installed a new OS it's the stock rom as far as i can tell.
Anyone have any ideas whats going wrong here or how to fix it?
thanks
edit: and apparently now I wiped the OS from the phone since it wont go past the LG logo. Is there some way for me to either copy a rom onto the phone from TWRP or copy a backup onto the phone? I've got a couple of TWRP backups saved on my pc, but since the phone wont start up I don't have any way of copying them onto the phone - damn non-user removable sd cards.
Click to expand...
Click to collapse
Can you boot to recovery?
If you can, then flash a newer TWRP build, they have MTP support, you can mount it while connected to your PC, copy a ROM zip over (there is a stock on in these threads somewhere), flash it from recovery, wipe everything first. Then you should be able to boot into a working device.
Yes I can boot into twrp, but I'm not sure how to copy files that way. I tried using adb but it couldnt find the phone. Can you give me some tips on how to copy a new ROM or twrp backup to the phone?
Thanks
merkk said:
Yes I can boot into twrp, but I'm not sure how to copy files that way. I tried using adb but it couldnt find the phone. Can you give me some tips on how to copy a new ROM or twrp backup to the phone?
Thanks
Click to expand...
Click to collapse
Yes, first thing is to flash this.
http://cubegamemc.de/kevinjoa/lollipop/recovery-geehrc/twrp/
You can flash it through fastboot.
follow these steps:
1. Download and place the file on your PC.
2. Reboot your device into Fastboot Mode. To do that, simply hold down the Volume DOWN+Power buttons together.
3. Once inside the Fastboot mode, connect your device to your PC via USB cable.
4. Launch a Command Prompt Window in the folder you saved the recovery image to. You can do that by holding down the Shift button on your keyboard and right-click on any blank area on the screen, then select Open command window here.
4. Enter the following command into the Command Prompt Window. You need to replace recoveryfilename.img with the actual name of the Recovery Image you downloaded.
Code:
fastboot flash recovery recoveryfilename.img
5. Once it is done, reboot your device
Code:
adb reboot recovery
should do it. If not, just hold down the power button, and get back to recovery.
at that point you should have the newest recovery. This recovery has MTP enabled so you can transfer files just like you can if you had a running device.
Once it shows up on you PC you can transfer a ROM zip or a backup to the internal SD. From there you I am sure you know how to flash a zip or restore a backup. It is the same as an older version. MTP should be under the "MOUNT" section of TWRP. I don't remember because I have a different device now.
Good luck!
If this doesn't work, follow the thread here: You would need the super big full bin file if you do though because you do not have a working ROM or zip currently on your internal SD card and this contains a very old recovery, but it does work.
http://forum.xda-developers.com/showthread.php?t=2230106
edit: I altered the directions from the source here for the att version. Don't worry, I changed them to suit your current need.
http://theunlockr.com/2013/03/26/how-to-install-twrp-recovery-on-the-lg-optimus-g-att/
My phone seems to behave a little differently than what you describe. Holding down the volume down and power button just turns it on. Holding vol up and power puts me into a screen with the android bot on it with the option to restart bootloader, go into recovery, or power off. and at the bottom there's some text indicating fastboot mode is on.
I was able to use the fastboot command to load the newer recovery. But for some reason, none of the adb commands work on my phone.
I'm copying a twrp backup to the phone now and i'll restore that. Hopefully that'll fix the issue of the phone not booting and if i am really lucky, fix the issue of the phone not being activated, but I'm not too hopeful about that.
Thanks again for all your help
hey - just wanted to say thank. Got my phone to boot back up again. Unfortunately the backup restore doesnt seem to have fixed my initial problem. Phone is back to saying it needs to be activated. Any ideas about that? It's also showing zero bars - not sure if that's what it's supposed to show when it's not activated.
Thanks again for your help
merkk said:
hey - just wanted to say thank. Got my phone to boot back up again. Unfortunately the backup restore doesnt seem to have fixed my initial problem. Phone is back to saying it needs to be activated. Any ideas about that? It's also showing zero bars - not sure if that's what it's supposed to show when it's not activated.
Thanks again for your help
Click to expand...
Click to collapse
EDIT:: TRY THIS FIRST<
Do a full wipe of the system and data, not internal. GO to recovery, select wipe, then factory reset. Then boot your phone. You will have to setup everything again but it might help. If it does not, you can always restore your backup again.
^^^^^^^^^^^^^^^^^^^^^^^
Interesting that your phone was the opposite for the buttons. Maybe I had it backwards, or maybe my source did. Either way I am glad you have a device that boots now.
Check this...
Go to the about section and see if your imei and other information are blank or have 0's. I am almost certain that there are 0000's.
If that's the case then you lost your EFS some how. and there is a way to recover that as long as you have a backup somewhere. You should have one somewhere if you used freegee to unlock your phone in the beginning. If not, perhaps an earlier backup you had of your device. A lot of the recoveries for this device make a backup of the EFS.
well i just dropped the phone off at a sprint repair store to see if they could do anything with it now that it actually boots. If they can't fix it, I'll try what you suggested. Although i already tried a factory reset and that didn't help.
well you are right about the esn/meid/IMEI - they are all zeros
I did a restore and then used freegee to restore the efs. Will free tell you if there is no backup of the EFS? Because i restored it, it finished pretty much instantly, and then i restarted the phone just be safe. Unfortunately it didn't fix it.
Phone still says searching for service, and now there's a little red x over the bars. Before the bars were blank but there was no red x. Not sure if that makes any difference.
Also, something else weird is going on now. I just tried copying a newer backup to the phone to try and restore the newer one. I don't seem to be able to copy files now. When i drag the folder windows , it says the device has stopped responding. If i try and copy each individual file in the backup folder, it starts to copy, and then just sits there like it froze, or like it's copying so slowly it might as well be frozen. I had to reflash twrp to the newer version and then I'm able to copy files.
Reloaded the efs backup again but still can't activate/have all zeros.
After a update for better compatibility for 3rd party app, my Zenfone wont get past the ASUS screen at all.
Im also stuck at the asus load screen. I played around with the permissions of the sd card, after rebooting its stuck. Guys how to unbrick?
bratski said:
Im also stuck at the asus load screen. I played around with the permissions of the sd card, after rebooting its stuck. Guys how to unbrick?
Click to expand...
Click to collapse
you may want to flash your phone back. so this consist of
1) read up how to access to Temp CWM
2) download and transfer the full rom to your SD card
3) do a wipe all partition and go to advanced setting, wipe cache
4) install zip and choose from external SD, point to that .zip file for the full rom and apply.
5) installation may take 10min or so do not switch it off. after installation you are good as new.
I believe this should solve your problem, normal if things get bricked is due to config file error could be [syntax, corrupted, missing, setting].
Flashing should solve mostly of it unless the file that you previously accessed require root and cwm does not give permission to the file. that is a permanent bricking.
As always, newbie should not try tweaking permission required files, you end up having bricking the device as there might be no solution to recover it due to access rights. ALWAYS have a back up file so you can at least copy the file back and chmod it.
jerk48 said:
After a update for better compatibility for 3rd party app, my Zenfone wont get past the ASUS screen at all.
Click to expand...
Click to collapse
by asus screen, did you mean the ASUS Setup Wizard?
sooty84 said:
you may want to flash your phone back. so this consist of
1) read up how to access to Temp CWM
2) download and transfer the full rom to your SD card
3) do a wipe all partition and go to advanced setting, wipe cache
4) install zip and choose from external SD, point to that .zip file for the full rom and apply.
5) installation may take 10min or so do not switch it off. after installation you are good as new.
I believe this should solve your problem, normal if things get bricked is due to config file error could be [syntax, corrupted, missing, setting].
Flashing should solve mostly of it unless the file that you previously accessed require root and cwm does not give permission to the file. that is a permanent bricking.
As always, newbie should not try tweaking permission required files, you end up having bricking the device as there might be no solution to recover it due to access rights. ALWAYS have a back up file so you can at least copy the file back and chmod it.
Click to expand...
Click to collapse
my problem right now is my pc wont detect my phone. Ive already installed the drivers.
Same thing happened to me when I tried flashing the OTA update with my phone being rooted. You have get into recovery mode on the phone and then use ADB to put the original image back to the device to get it back to stock so it will reboot. It worked for me
sooty84 said:
you may want to flash your phone back. so this consist of
1) read up how to access to Temp CWM
2) download and transfer the full rom to your SD card
3) do a wipe all partition and go to advanced setting, wipe cache
4) install zip and choose from external SD, point to that .zip file for the full rom and apply.
5) installation may take 10min or so do not switch it off. after installation you are good as new.
I believe this should solve your problem, normal if things get bricked is due to config file error could be [syntax, corrupted, missing, setting].
Flashing should solve mostly of it unless the file that you previously accessed require root and cwm does not give permission to the file. that is a permanent bricking.
As always, newbie should not try tweaking permission required files, you end up having bricking the device as there might be no solution to recover it due to access rights. ALWAYS have a back up file so you can at least copy the file back and chmod it.
Click to expand...
Click to collapse
downshift00 said:
Same thing happened to me when I tried flashing the OTA update with my phone being rooted. You have get into recovery mode on the phone and then use ADB to put the original image back to the device to get it back to stock so it will reboot. It worked for me
Click to expand...
Click to collapse
where do i get the stock image?
bratski said:
where do i get the stock image?
Click to expand...
Click to collapse
here is the stock firmware.
https://www.asus.com/Phones/ZenFone_2_ZE551ML/HelpDesk_Download/
its fine if your phone does not talk to your PC now. copy the firmware to your SD card via other means. [card reader etc]
then try my method of flashing it back to original state, you stated that adb dont work, have you tried the temp CWM method yet?
the main goal is to wipe dalvik cache under advanced menu in CWM, and cache partition and all hard reset.
then you flash back your original file.
hope it works for you.
sooty84 said:
here is the stock firmware.
https://www.asus.com/Phones/ZenFone_2_ZE551ML/HelpDesk_Download/
its fine if your phone does not talk to your PC now. copy the firmware to your SD card via other means. [card reader etc]
then try my method of flashing it back to original state, you stated that adb dont work, have you tried the temp CWM method yet?
the main goal is to wipe dalvik cache under advanced menu in CWM, and cache partition and all hard reset.
then you flash back your original file.
hope it works for you.
Click to expand...
Click to collapse
ive read about the temp cmw method and i cant figure out how to go about it. it says on the instruction that you need to turn on phone before running the cai_dat_CWM. how am i going to do this as my phone will only boot to the asus logo? thanks
just figured it out. I need to boot in fastboot so the phone will get recognized. However, the latest build available on the asus website is still 2.17.40.12. I already have the 2.18.40.12 version. The 2.17 firmware can't overwrite the newer build in temp CWM recovery. Anybody knows where i can download the full rom? Z00A-WW-2.18.40.12?
bratski said:
just figured it out. I need to boot in fastboot so the phone will get recognized. However, the latest build available on the asus website is still 2.17.40.12. I already have the 2.18.40.12 version. The 2.17 firmware can't overwrite the newer build in temp CWM recovery. Anybody knows where i can download the full rom? Z00A-WW-2.18.40.12?
Click to expand...
Click to collapse
I GOT THE SAME PROBLEM.
dunno what to do anymore.
sigh...
help me please
Ninjakura said:
I GOT THE SAME PROBLEM.
dunno what to do anymore.
sigh...
help me please
Click to expand...
Click to collapse
here is the link for stock but pre-rooted img for latest 2.18.40.12 firmware,,make sure to download Z00A firmware if you have ZE551ML device.. and if I was not mistaken, you may choose to FULL UNROOT in SuperSU apps to go back to stock rom..
cangcan said:
here is the link for stock but pre-rooted img for latest 2.18.40.12 firmware,,make sure to download Z00A firmware if you have ZE551ML device.. and if I was not mistaken, you may choose to FULL UNROOT in SuperSU apps to go back to stock rom..
Click to expand...
Click to collapse
thanks. problem solved after i followed instructions from this thread, http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
bratski said:
my problem right now is my pc wont detect my phone. Ive already installed the drivers.
Click to expand...
Click to collapse
me too, any idea on how to fix it?
sooty84 said:
you may want to flash your phone back. so this consist of
1) read up how to access to Temp CWM
2) download and transfer the full rom to your SD card
3) do a wipe all partition and go to advanced setting, wipe cache
4) install zip and choose from external SD, point to that .zip file for the full rom and apply.
5) installation may take 10min or so do not switch it off. after installation you are good as new.
I believe this should solve your problem, normal if things get bricked is due to config file error could be [syntax, corrupted, missing, setting].
Flashing should solve mostly of it unless the file that you previously accessed require root and cwm does not give permission to the file. that is a permanent bricking.
As always, newbie should not try tweaking permission required files, you end up having bricking the device as there might be no solution to recover it due to access rights. ALWAYS have a back up file so you can at least copy the file back and chmod it.
Click to expand...
Click to collapse
I have same prolem as OP's got.
I've got stuck on Asus Loading screen after install OTA update on rooted device.
I'm gonna try your method.
Thanks
downshift00 said:
Same thing happened to me when I tried flashing the OTA update with my phone being rooted. You have get into recovery mode on the phone and then use ADB to put the original image back to the device to get it back to stock so it will reboot. It worked for me
Click to expand...
Click to collapse
how did u do that? can u give me step by step instruction please?
ty
Did anyone able to fix this problem (stuck at Asus logo and not able to get to recovery mode or connect to the computer)? Thanks!
SAN_MARINO said:
Did anyone able to fix this problem (stuck at Asus logo and not able to get to recovery mode or connect to the computer)? Thanks!
Click to expand...
Click to collapse
Press Power+Volume Up key, After vibration leave Power Button then choose Recovery Mode using Volume keys, if sleeping Android screen appear at Recovery with Error message, Press Volume Up and Power and leave immediately Power Key, it will show you the Recovery Menu, then Reset your device, it will solve your problem.
If I am helped you, Press Thanks button.
k576 said:
Press Power+Volume Up key, After vibration leave Power Button then choose Recovery Mode using Volume keys, if sleeping Android screen appear at Recovery with Error message, Press Volume Up and Power and leave immediately Power Key, it will show you the Recovery Menu, then Reset your device, it will solve your problem.
If I am helped you, Press Thanks button.
Click to expand...
Click to collapse
Thanks!
I already tried it like 20 or more times. The ASUS logo still shown for like 10 seconds and died and came back again (ASUS logo). When I tried to connect it with my laptop, the computer won't recognize the device.
SAN_MARINO said:
Thanks!
I already tried it like 20 or more times. The ASUS logo still shown for like 10 seconds and died and came back again (ASUS logo). When I tried to connect it with my laptop, the computer won't recognize the device.
Click to expand...
Click to collapse
I will try to tell you step by step:
1. Press Power Button + Volume Button
You enter into Recovery Fastboot Option, then Choose Recovery menu using Volume Key (3 Option mostly shown)
then press Power Button (From Recovery Mode), it restart.
2. Then after Restart it shows you (Mostly) Sleeping Android Screen with Error text, then Press First Volume Up Button, and Press Power Button (Power button for a second or two then leave it, IF YOU PRESS MORE TIME, IT WILL RESTART THE PHONE).
3. You can now see the Recovery Menu with Normally appear in other phones also - Reset, Restart, Etc Option.
Hope you will now able to reset your phone...
----------------------------------------------------------
PRESS THANKS BUTTON IF I AM HELPED YOU
----------------------------------------------------------
NO ONE?????
ODIN --> Flash Stock Recovery (AP) with NAND Erase All Option Checked (because it seemed to make sense) + Auto Reboot + F. Time Reset --> Reboots to Stock Recovery (did not work before) --> Reboot into Recovery --> Wipe Data/Cache and Dalvik just to be safe (this crashed it before) --> Reboot. THE END
TL/DR: I am currently stuck on recovery/update mode. Any attempt to wipe data or clear dalvik crashes it. any attempt to access data through TWRP crashes it. Flashing stock rom or custom rom does not help. Somethings wrong with /data? It thinks it has root from the CF Auto Root, but does not really? Something wrong with partitions? Should I wipe the nand with ODIN 3.10? Repartition? ugh ... Please help ...
I have searched the forums and found nothing that describes this issue precisely. I have also tried to apply various suggestions to repair, which, for the most part seems to have made it worse. I am hoping that people still look at this forum.
PC - Windows 7
Initially @4.2.2 ---> Touchwiz debloated stock ROM which I rooted. It worked for a couple years, but the device crashed frequently. I do not recall much about the installation, but believe that I used CWM/TWRP at the time. After installing the ROM, I ran triangle away (out of the box, it had 4.1.2, i recall)
I decided to upgrade to the most recent stock ROM (4.4.2). In order to do so, I used an easy installer I found else where on XDA. (http://forum.xda-developers.com/showthread.php?t=2773712 ---ODIN One Click exe). The device was not initially recognized, so I reinstalled the official driver package (said that they already existed, but I installed again anyway). Ran 1-click and it appeared to work.
Initially, the device booted (long startup) and seemed to function. It also preserved all data and programs (presumably did not touch the internal memory - 16 GB) and possibly root /data.
I then tried to root through most recent ODIN with CF auto root. This appeared to work and rebooted (again, showing the updating android apps screen before fully booting).
The only thing that i could find that had changed was the wallpaper (showed on lock screen but not on home screen). I could no longer find the image, so tried to go to /data/data to find it with root explorer equivalent. This is where it started to act weird.
NOTE: I did not clear anything (system cache, etc. at any point)<--a lie (see below)
It showed the root folder fine, but when I clicked on /data it took a while and could not access it. It either rebooted itself or I rebooted, but this time it was stuck in a boot logo loop. I entered download mode and flashed TWRP through ODIN. I set it to not reboot automatically so that the bootloader was not overwritten automatically (thus losing recovery). TWRP came up. The computer recognized it as a Media Device after I mounted USB storage. Just in case, I copied all of the important files from the internal SD Card to my computer. I then tried to go to the file explorer to copy the wall paper and it forced a reboot. At this point it was stuck on a logo screen boot loop again. I was able to enter Download mode and reflash TWRP. This allowed me to enter recovery again, however, now it would only boot directly into recovery (or Download mode if I did the button combo). The interesting thing was that it would reboot two or three times before successfully entering TWRP.
I believe I tried to reflash the stock ROM at this point, which might have worked but made no difference.
I was also having a lot of problems getting Windows to properly recognize the device. I had to reinstall the drivers a couple times. I tried Kies after the problems started and it tried to connect by failed. The diagnose connection did not work either. I was not able to get Kies to connect though I tried several times throughout the attempted repair
I downloaded a stock-rooted 4.4.2 ROM from here and tried to flash it. It failed.
I also tried to flash via Heimdall, but initially could not find any stock ROMs for Heimdall for the Galaxy 8. (The driver utility that is included helped to get the phone recognized by Windows sporadically).
I decided to switch over to CWM touch recovery, which I flashed via ODIN (I was having issues with TWRP again and also could not get windows to recognize the device as a media device when I mounted USB storage). This worked after a couple tries and I was able to enter CWM. I attempted to flash the stock ROM but it failed. Either at that point or when I tried to mount data it returned an error that device did not have root. Again, it would only boot into CWM (on its own) or Download mode (with key combo). At some point around here I cleared the cache and dalvik (error) after it returned an error saying insufficient space when trying to flash ROM.
I dissected the .exe from the autoflash used in the beginning (stock unrooted 4.4.2) and used the contents (system.img, cache.img, hidden.img, tz.img, recovery.img and one other I do not remember) in Heimdall to create a Heimdall package. At this point I figured out I did not need to create the package, but just specify the individual files. I flashed. It appeared to complete System.img successfully and then failed. Tried again with the same result.
Now when I rebooted, it would enter download mode with the Key combo, but otherwise it booted instantly to an error screen to the effect that a firmware installation had failed and to use the repair function in Kies to fix. Kies still did not recognize it.
At this point, I figured I should stop. Currently I can get to the download screen or the error screen. The computer recognizes it but intermittently fails to install driver. Zadig.exe sees it as Gadget Serial. Sometimes Windows just sees it as SAMSUNG_Android, in which case drivers fail. Once or twice I got it to recognize it as Samsung USB Composite Device, but Kies would still not work.
That's all i have for now. If more information is needed, let me know and I will update the post when I get home from work tonight (this is from memory).
Thank you
UPDATE: last night I went home and was able to get it back to the point where I could flash TWRP or CWM recovery. If I try to flash Stock Recovery, it fails. A minor problem is that I cannot turn it off - it just turns it self on again, so the battery keeps running down.