Related
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
Hello all, for the past few days I have been trying to install android 4.0 ICS on my HTC Wildfire S CDMA phone, currently connected to youtube. on one instance I accidently formatted my backup so at this point im prettty scared.
I have already tried full resets, clearing memory, batttery, cache etc. I am stuck using CWM because TWRP touch screen doesnt seem to work at all. All help will be greatly appreciated. thank you.
I have also tried most of what is on other forums such as kernel update, redownloading.
I also find that if while installing, the phone restarts on its own. at first I thought the installation was done but to my dismay, it wasnt....
I'm not sure I can help but I would suggest you try to clarify what you are asking and trying to do. You state that you're doing an install of ICS 4.0 on your WFSc. I don't think any WFS, gsm or cdma got the ICS update unless you mean as Cyanogen Mod 9 or some other ROM? You also said something about being connected to You Tube now...that doesn't make sense.
That being said, if you meant you were trying to install the ICS theme then you might get a quicker more focused response if you posted in this forum:
http://forum.xda-developers.com/showthread.php?t=1504935
Clarification
I got a second wildfire s from my cousin. exact same model and was bought the exact time as my current one and it successfully installed the cynanogen 9 with the only failure being that the touchscreen is inoperable but I will work on that another time. also when I said connected to youtube, I meant I tried to look on youtube for fixes but never found one. anyway the main problem is that my phone stops midway through the "installin updates" to either freeze or restart to a blank operating system "meaning its stuck on the htc logo". I hope this clarifies what I was trying to convey in the previous post and I promise to keep a closer eye for any other messages. I also thank you for answering.
Instead of potentially aggravating you with 20 questions, I'll just briefly run thru the steps, FWIW. I see you mention CWM.
-So, you probably unlocked the booloader at HTC dev and are S-on.
-Installed CWM, so you have the adb files and htc sync on your computer.
-Rooted, although flashing CM will root.
-Battery charged.
-Downloaded the correct CM9 for your WFS, i.e., gsm or cdma, and moved it to your sd card after extracting the boot.img file and putting it into the folder on your computer with the adb, fastboot, etc. files for later.
-Booted into CWM and wiped the cache, dalvik-cache, and data/factory reset.
-Selected the CM9 file on your zip, and started the install.
I'm a little unsure what you are saying happens next, but normally you would:
-after CM9 is flashed go to fastboot in the bootloader or reboot into recovery>fastboot.
-Attach the USB cable from the computer to the phone and with the command prompt at that folder where you have those adb files type:
fastboot flash boot boot.img and press enter
-Then reboot and CM9 should load...unless now both of us have missed something ::yikes!::
For some reason most guides seem to skip that part about extracting the boot.img file and flashing it after the ROM install, which is needed if the phone is still S-on. Typically seen when stuck on the HTC logo after flashing the ROM and rebooting, and you mentioned being stuck on the HTC logo. If the phone is S-off, the boot.img gets flashed from within the ROM during the install.
Hope I found the missing step and that it installs successfully.
romemo two
MiCeltic said:
Instead of potentially aggravating you with 20 questions, I'll just briefly run thru the steps, FWIW. I see you mention CWM.
-So, you probably unlocked the booloader at HTC dev and are S-on.
-Installed CWM, so you have the adb files and htc sync on your computer.
-Rooted, although flashing CM will root.
-Battery charged.
-Downloaded the correct CM9 for your WFS, i.e., gsm or cdma, and moved it to your sd card after extracting the boot.img file and putting it into the folder on your computer with the adb, fastboot, etc. files for later.
-Booted into CWM and wiped the cache, dalvik-cache, and data/factory reset.
-Selected the CM9 file on your zip, and started the install.
I'm a little unsure what you are saying happens next, but normally you would:
-after CM9 is flashed go to fastboot in the bootloader or reboot into recovery>fastboot.
-Attach the USB cable from the computer to the phone and with the command prompt at that folder where you have those adb files type:
fastboot flash boot boot.img and press enter
-Then reboot and CM9 should load...unless now both of us have missed something ::yikes!::
For some reason most guides seem to skip that part about extracting the boot.img file and flashing it after the ROM install, which is needed if the phone is still S-on. Typically seen when stuck on the HTC logo after flashing the ROM and rebooting, and you mentioned being stuck on the HTC logo. If the phone is S-off, the boot.img gets flashed from within the ROM during the install.
Hope I found the missing step and that it installs successfully.
Click to expand...
Click to collapse
Thanks again for the reply. you have given me quite a lot of information and 90% of it was correct and dead on, but where you misunderstand is that while using CWM and flashing ANY Rom onto the phone, it either freezes at "installing updates" or restats if it ever gets to the next step. The confusing part of this is that the other phone which is the exact same model was able to be flashed with all the roms that I tried on my own phone with no problem.
To make things easier. after this I will adress the phones differently:
My phone (Not working Flash) is Marvelc 1
My cousins phone (working flash) is Marvelc 2
This is particularly challenging because you keep emphasizing that you are doing exactly what (you did?) on the other WFS, and I presume they have identical hboots (which they'd have to if you unlocked using htcdev). You also say that you re-downloaded the different files (recovery, CM9) and double checked that their for the MarvelC, and re-did then, re-tried, re-tried, re-tried...and I'm presuming that when you were re-trying that you didn't skip any steps, like the wipes. Oh, and most of all that everything worked on this phone before you started unlocking - flashing the recovery - and rooting. I thought about htc sync and adb, but the fail point is not when the computer is hooked up.
So all that being re-hashed, I'm looking for something concrete, a clue from what you've said or hinted at and right now I'm curious about your SD card. That is most likely not common to both phones and you did say, "on one instance I accidently formatted my backup..." Did you get everything formatted OK with no errors...that SD especially, as Fat32, shouldn't need an ext partition at this time. It could be corrupted and failing at some point when it's unpacking CM9, or whatever. You might re-do formatting that, including doing it on a computer if you have an adapter or a card reader, if not in CWM. It wouldn't hurt to put it in another phone and see if you can read it there and/or on a computer when that other phone is hooked up as a disk drive. Then put a fresh copy of whichever CM9 your flashing on it and try EVERYTHING one more time (back in your phone of course) ::haha:: be sure to leave the battery out for at least 30 sec. after all this and before trying the flash just to be sure any residual static in the phone has dissipated.
If it fails again, leave on and hook up to the computer and run: "adb logcat" from the prompt where you have your adb files and see if it will show you anything. You can exit logcat with the Ctrl + C keys. What do you think?
Oh, and while you're doing all that, who's CM9 are you trying to install. Do you have a link so I can look at it out of curiosity?
It took me awhile to absorb all that but after trying all.those steps,.there was no progress. Furthermore the microsd card I use is for both of my HTC's. And lastly the adb logcat or any adb script for that matter won't work unless the phone is in debug mode with a working o.s.
Thanks for hanging with me and I look forward to your next suggestion.
Sent from my HTC-PG762 using xda app-developers app
I wasn't sure whether there would be some kind of script running in a buffer of the install that might be captured with something like: logcat -b event > /sdcard/logcat.txt
so it was a shot in the dark and I don't know what's left, but perhaps someone else that is reading the post might have some ideas, or experience with this specific issue and jump in with a solution.
I was writing a macro once and couldn't get it to work and spent too much time over 3 days trying to figure it out. When I finally asked someone else to look at it, I was just missing a semi-colon or some one simple thing. You sound pretty knowledgeable, sorry I couldn't be the second set of eyes to come up with the missing thing. If I can think of anything more, I'm subscribed to this thread and I'll surely suggest it.
Thank you for trying, I hope to find an answer soon enough.
Sent from my HTC-PG762 using xda app-developers app
Here's what I did and where I'm at please help if you can? **MOVED TO CORRECT FORUM **
Originally I tried to root but it didn't root. In fact my phone started to have issues right after my attempt to root.
PHONE: Tmobile Samsung galaxy S2 SGHT989 loaded w Jelly Bean 4.1.2
WHAT I DID: I followed this guide to root my phone (it didn’t work/root, even though the Recovery message said it rooted)
**I'm sorry for referencing another forum..I just googled a how to**
downloaded extracted: ODIN 1.85
downloaded: TWRP (touch recovery 2.5.0)
downloaded to pc then put on SD card: Superuser – CWM_ROOT_SUPERUSER_3.1.3_BUSYBOX
*THEN I FOLLOWED THE REST OF THE GUIDE ON HOW TO ROOT..very meticulously (the guide shows CWM recovery but I used TWRP recovery).
From TWRP I selected and ran the zipfile for Superuser (the CWM***BUSY BOX file).
I got the message that said that I was rooted.
I rebooted the phone and downloaded the Titanium Backup app because it requires root. I got the message from Titanium Backup app that said I wasn’t rooted.
The guide says that if it’s not rooted then to go back to recovery/TWRP and flash Superuser again. I did and it STILL didn’t work.
I tried reloading the cwm recovery as well (both CLOCKWORD MOD RECOVERY I thought maybe this was the issue “nope” and then back to TWRP because it’s easier to use).
After this it started doing the endless “BOOTLOOP”. I had to take out the battery to stop it.
I tried going into MASTER RESET from boot “volume down, power, home key” it didn’t work..still BOOTLOOP.
So I rebooted into recovery/TWRP to wipe thinking that this might fix it. I wiped out everything including the OS (I got a message when I was about to reboot that said “you don’t have an OS, do you want to proceed reboot?”.
In my attempt to unbrick my phone I tried to go through Kies but it didn't recognize my phone (I checked the model & serial number 4-5 times).
So I downloaded the stock ROM through samsung updates so I could flash the ROM with ODIN. I started made sure auto reboot f.reset time was checked, clicked PDA, browsed to the file, highlighted the file and when I clicked "open" to add the file it doesn't show the path in PDA section as it usually does. So ODIN won't let me flash the stock ROM.
I don't think the file's corrupted because I downloaded the stock ROM from 2 sites multiple times, I tried switching USB ports, switched USB cables, rebooted PC, restarted odin. I can't get it to recognize the file.
I'm at my wits end so if anybody can assist I'd be very grateful.
Thank you for your time and help
raymondhs said:
Here's what I did and where I'm at please help if you can? **MOVED TO CORRECT FORUM **
Originally I tried to root but it didn't root. In fact my phone started to have issues right after my attempt to root.
PHONE: Tmobile Samsung galaxy S2 SGHT989 loaded w Jelly Bean 4.1.2
WHAT I DID: I followed this guide to root my phone (it didn’t work/root, even though the Recovery message said it rooted)
**I'm sorry for referencing another forum..I just googled a how to**
downloaded extracted: ODIN 1.85
downloaded: TWRP (touch recovery 2.5.0)
downloaded to pc then put on SD card: Superuser – CWM_ROOT_SUPERUSER_3.1.3_BUSYBOX
*THEN I FOLLOWED THE REST OF THE GUIDE ON HOW TO ROOT..very meticulously (the guide shows CWM recovery but I used TWRP recovery).
From TWRP I selected and ran the zipfile for Superuser (the CWM***BUSY BOX file).
I got the message that said that I was rooted.
I rebooted the phone and downloaded the Titanium Backup app because it requires root. I got the message from Titanium Backup app that said I wasn’t rooted.
The guide says that if it’s not rooted then to go back to recovery/TWRP and flash Superuser again. I did and it STILL didn’t work.
I tried reloading the cwm recovery as well (both CLOCKWORD MOD RECOVERY I thought maybe this was the issue “nope” and then back to TWRP because it’s easier to use).
After this it started doing the endless “BOOTLOOP”. I had to take out the battery to stop it.
I tried going into MASTER RESET from boot “volume down, power, home key” it didn’t work..still BOOTLOOP.
So I rebooted into recovery/TWRP to wipe thinking that this might fix it. I wiped out everything including the OS (I got a message when I was about to reboot that said “you don’t have an OS, do you want to proceed reboot?”.
In my attempt to unbrick my phone I tried to go through Kies but it didn't recognize my phone (I checked the model & serial number 4-5 times).
So I downloaded the stock ROM through samsung updates so I could flash the ROM with ODIN. I started made sure auto reboot f.reset time was checked, clicked PDA, browsed to the file, highlighted the file and when I clicked "open" to add the file it doesn't show the path in PDA section as it usually does. So ODIN won't let me flash the stock ROM.
I don't think the file's corrupted because I downloaded the stock ROM from 2 sites multiple times, I tried switching USB ports, switched USB cables, rebooted PC, restarted odin. I can't get it to recognize the file.
I'm at my wits end so if anybody can assist I'd be very grateful.
Thank you for your time and help
Click to expand...
Click to collapse
https://www.dropbox.com/s/vxapb57yeuk60ud/T989UVMC6_T989TMBMC6_TMB.zip
try unzipping this file- place .tar file on desktop
when your connected ond open odin, click pda , search desktop and add .tar file -hope this helps
Ok..so that I don't mess this up.
after I download this to desk top should I not open the zip file? Just open up ODIN select PDA then browse to the file location?
I'm screwing something up here...
raymondhs said:
Ok..so that I don't mess this up.
after I download this to desk top should I not open the zip file? Just open up ODIN select PDA then browse to the file location?
I'm screwing something up here...
Click to expand...
Click to collapse
did you get pm
Hallelujah!
UNBRICKED :victory: Up and running...phew!!
Thanks Fasted12! If you were here I would hug ya and make you feel uncomfortable. Stay awesome :good:
So I made a post in the general help thread and nobody has replied (although I've only waited a few days so I could probably wait a bit longer) but still I feel like my phone's issues are "unique" compared to other bootloops, I can't find anyone else having the same symptoms on their phone. I'll repost what I said in the general help thread and then give a brief overview of everything because I simply cannot comprehend why I'm unable to get out of bootloop with this damn phone.
So I just recently picked up an old Zenfone 2 (ZE500CL) off of my father who didn't really need it anymore and it was an upgrade from my old ****ty phone, so of course I wanted to root it and after using it for a few hours I wanted to install a custom rom by unlocking the bootloader. Well, I tried that, and something must have gone wrong because I got a bootloop and was only really able to boot into recovery mode.
Now, I didn't backup because I'm dumb for one and two I generally have a good idea of where to start if something does go wrong. The thing is, the methods I've looked up and tried have all failed. First, reflashing the stock rom of my ZE500CL (I've tried four different firmwares from the official website, and I know it's ZE500CL because that's what recovery mode is telling me) does not work. Adb hits 47% in the command prompt, the phone stays at 25% until then, and it goes:
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted
Not sure why it doesn't work, I looked it up and tried various things and it just isn't resolving itself.
So I tried simply running commands like the following:
fastboot flash recovery recovery.img
Using files from the stock firmwares themselves, and that gives me a flash_cmds error. I've tried deleting all of the userdata, the system, the cache, and a factory reset through recovery mode but none of that works. I'd really appreciate any help anyone could offer, this is a pickle and I'd really like to get this phone back up so that I can just run it as a rooted phone.
Click to expand...
Click to collapse
Now, I'll go over the issues quickly:
I'm stuck in bootloop but I can get into recovery mode
Trying to flash any rom, including multiple stock roms from the asus website, results in an installation aborted message at 47% in either ADB or microSD attempt at flashing the rom.
Attempting to run commands like fastboot flash recovery recovery.img ends up giving me a flash_cmds error which I cannot find anywhere else for the Zenfone 2e
Deleting the cache, userdata, system, or factory resetting the phone does not remove the bootloop
Unlocking and relocking the bootloader does nothing
I would really appreciate any help, feels like my phone is a lost cause even when it's not hard bricked.
Try ASUS Flashtool with a .RAW Firmware...
Find on This Thread...
ponnuvelpandian said:
Try ASUS Flashtool with a .RAW Firmware...
Find on This Thread...
Click to expand...
Click to collapse
Thanks, I haven't seen this. I've got the Intel and xFSTK drivers all up and running but my phone isn't being recognized constantly by my computer under Intel Soc in my Driver Manager, and it's not being recognized as MOOREFIELD but rather as CLOVERVIEW PLUS, and only for a second in-between boots on my phone. Can't get the files to be downloaded through xFSTK, so I've hit a snag here unless someone knows the solution to this.
I'll try just running the flash tool and using a raw firmware, then, since I can't do any of the other stuff.
EDIT: Looks like the issue I was having before is stopping me from running the tool, seems that the computer needs to recognize my phone through the Intel drivers at all time (which it doesn't) in order to run the tool. Also I can't get the tool to view the raw file, it only seems to read zip files (so I put the raw into an empty zip, thinking that could maybe work but I don't know for sure). Damnit, I don't know why this is so difficult.
EDIT 2: All right! Looks like I got it working. The process was relatively simple, actually. It involved booting into TWRP but I wasn't able to most of the time for some reason, it would just never do it. But, I was able to using the CWM Zenfone 2 bat file located here: http://forum.xda-developers.com/zenfone2/help/ze500cl-rooting-related-stuff-t3163528/
Then, I needed the stock rom for my ZE550CL placed onto an external sd card which can be found here: http://forum.xda-developers.com/zenfone2/help/ze550cl-factory-reset-return-to-stock-t3141513
So I would download the CWM Zenfone 2, replace the recovery file as the post states, then run the file. After that, I would run T4 since T1 and T2 didn't work (never tried T3), only T4 would seem to boot me into TWRP. From there, I went to Install, left Zip Verification unchecked, and let the damn thing run. It was the only thing that would run for me, even when doing it with ADB it wouldn't work with the stock rom. Then, I just rebooted and now I'm back on my phone. Hopefully this helps anyone else having this troubling issue, it was terrible!
Hello, sorry for the generic title, but i'm quite the noob about android modding and stuff.
Anyway I wanted to root my phone, just to stream some music to my stereo system. How naive I was...
So I unlocked the bootloader, installed twrp with adb and SuperSU with twrp. Everything was fine and phone was rooted but my past naive me thought "well let's try a custom rom, why not". So I went forth and downloaded some stuff from getdroidtips and what I understood is that all I needed to do was to do a wipe, then install the zip file via twrp. I did that and didn't work. After that I realized I made a crucial mistake: I didn't backup my phone from twrp, so I was there with no OS, quite panicked and frustrated. So I tried some other roms, finally I got one that worked, this: https://forum.xda-developers.com/honor-7x/development/openkirin-aosp-8-0-honor-7x-t3746257
It works but it's barebones and on boot it shows a message: "There's an internal problem with your device. Contact your manifacturer for details.". So, I tried recovering from HiSuite, recovery mode etc but nothing worked, I reinstalled SuperSU in the new OS via twrp to see if that would help somehow, but no. in the end I had the even more naive thought that maybe unrooting would allow me to repair via hi suite or something, so I mindlessly selected "complete unroot" on the SuperSU app, and this was the second big mistake, the process somehow ****ed up the twrp install and it no longer works. Instead, if I try to enter twrp with power button + volume up button, it shows the regular "your phone has been unlocked" screen and then comes up for a split second a black screen with, on the bottom half of the screen the "no command" logo, under it some lines of code that I can't read. It suddenly disappears and sometimes enters in a bootloop showing this screen and powering off every time.
If I keep power button pressed bootloop ends and the phone boots "regularly" in the openkirin OS.
I tried reinstalling twrp the same way I did the first time. No error on adb but same no command behaviour
So what I got now is:
kind of bootlooping no command window
openkirin OS with internal problem message
fastboot and rescue mode
it seems to work on adb (everything is fine if I type adb devices)
not working HiSuite recovery
not working Huawei eRecovery
not working download mode (I guess? the power+volume up+volume down combination)
Maybe I should mention I also did a data wipe (?? the option on the right next to "advanced wipe" in the Wipe screen, if I remember correctly) in twrp before installing openkirin, it was suggested on a yt video about how to install openkirin. And that, at a stage I tried using MultiTool but it gives me an error: "exception during a web client request. Error#9", while at the bottom left it says "downloading AdbWinUsbApi.dll..."
Sorry for the general noobishness and the bad english that might be there.
So, any tips for bringing back the phone to normal? Or at least repair twrp??
Please help, I hate needing to throw this phone away just because I wanted to stream some music and because of a couple of stupid errors
Sorry for not answering earlier. It seems, between TWRP and stock recovery, you have messed up I think. When there is no proper recovery it become difficult to bring back the phone. You should try to put it in fastboot mode first, by powering off, pressing the volume lower button and connecting it to computer. Try installing TWRP and flash a custom rom other than openkirin from there if possible. Fastboot is the choice to go if recovery is messed up.
sdivk said:
Sorry for not answering earlier. It seems, between TWRP and stock recovery, you have messed up I think. When there is no proper recovery it become difficult to bring back the phone. You should try to put it in fastboot mode first, by powering off, pressing the volume lower button and connecting it to computer. Try installing TWRP and flash a custom rom other than openkirin from there if possible. Fastboot is the choice to go if recovery is messed up.
Click to expand...
Click to collapse
No worries, I managed to fix it anyway. Some things might be obvious but I'll share what I did nevertheless, in case some other newbie finds himself in a similar situation.
So there was seemingly no way of reinstalling twrp nor the stock recovery. But luck came my way and by almost random clicking I found out that, even if multitool closed as soon as I clicked the ok button in the error message, if I simply ignored the error, the program worked just fine (as I write this I installed another version and it gave no error message). So I played with it a bit and found out that it can flash twrp and it does not need a file from you, it already has a twrp version ready to install. I did that and it worked. It looks like the first twrp file I used didn't work anymore or was someway corrupted by the countless things I tried. So, with twrp working again I was able to backup the sloppy openkiring OS and try the unbrick tool. So I browsed the internet for a guide. Guides always mention as the first step for unbricking using the VENDOR.img file located inside a full stock rom. Problem is, 99% of the times they provide a rom without the needed file. So after some tries I found a good complete stock rom with the VENDOR.img here: drive.google.com/file/d/1tjHefytEWbpuV1f4YjX8AaSMzT6jr8TQ/view but I can't remember which forum/site I found it in.
I followed the guide which involves:
-extracting the UPDATE.APP file contained in the provided zip with huawei extractor tool into an X folder on your pc
-copying the VENDOR.img file contained in the X folder, on the root folder of the sd card
-backing up OS (if there's any) via twrp (I had something like 50 partitions, I guess that was messing things up a bit, but for safety I backed them all up)
-doing an advanced wipe from twrp selecting ALL checkboxes BESIDES the SDcard of course
-flashing the vendor.img file via twrp selecting the "Vendor" partition when prompted
-downloading the update_full_[your model]_hw_[your region].zip file, in my case update_full_BND-L21C_hw_eu.zip
-extracting the UPDATE.APP file contained in update_full_BND-L21C_hw_eu.zip with Huawei extractor tool in some other folder Y
-looking for a file named cust.img/CUST.img/version.img/other_name.img (I don't know which other names it can have, I was lucky and had a VERSION.img file in it)
-rename the cust.img/CUST.img/version.img/other_name.img to CUST.img and copy it from the Y folder to the X folder
-boot your phone into fastboot mode
-connect phone to multitool via usb and select the "unbrick" tab
-there, Multitool asks for a folder, give it the X folder. There are some checkmarks on the Multitool "unbrick" page. 4/5 of them should become checked after the folder input. In my case the first 4
-then, simply press the unbrick button
-wait and pray (it can look like it freezes while it's copying the system.img file but wait, it'll be fine)
So I did that and it worked flawlessly, the phone booted slowly but surely into EMUI 5.1 with Android 7.0 I think and everything was fine.
At that point I had a working OS and a working twrp but wanted to go back to the OS I was used to, Android 8.something so, I tried connecting the thing to HiSuite and it automatically asked if I wanted to update, not to 8.something but to 9.1. I thought "SURE I DO!" and updated flawlessly (I thought 9.1 hadn't even been released here in Italy).
When it booted I found out the new OS was working like an antivirusless xp pc: it didn't recognise the SIM, it would crash every 20 seconds, app downloads got stuck at 99%, if it felt like it, it rebooted, pc connection was not stable. Besides, the update being "official" and installed from "trusted" sources (HiSuite), it completely wiped twrp.
And that was the "OH ****, here we go again" moment: no twrp and worse-than-ever-working OS.
So because of the new EMUI version, I guess, Multitool kept recognizing the phone but stopped offering its own recovery, eRecovery, twrp files available for flashing. I was completely frustrated with all of this and decided to give up, but I made the last effort: I tried the relock function in multitool. So I provided the key, pressed relock, waited, prayed, and finally cheered. It worked like a charm. Phone runs now on EMUI 9.1 with locked bootloader without problems. Finally
So I guess in the end I payed 4 euros for a nice update, a painful and frustrating trip into android modding and a lesson : never do android modding!
no, just kidding, don't do it just if you are a newbie AND you don't want to risk to throw the phone in the grabage.
In all other cases consider it carefully
Oh, and also, God bless the MT Team and Russia altogether!! thanks
Quite an experience. All the best. ?
Lol sounds fun. I've bricked my Huawei Mate SE/Honor 7x more times than I can count. I'm just awaiting my 9.1. I want my GPU Turbo! Is it as good as it's supposed to be?