Related
Hi all,
Here is my sad saga.
Today, I decided I wanted to move up to ICS. I had 2.3.4 on a Koodoo phone that I decided was ready for the brave new world of ICS (bought it off Kijiji, now running it on Rogers which means I have no option of bringing it into a shop).
Ran into some issues but some good folks saved my butt in a number of tough spots. However, my grave seems to have been dug deeper by the minute. Essentially, I have managed to upgrade to 4.0.3. but am stuck with no 3G connection, hence no phone signal. This is a HUGE issue since I require my phone for work (foolish move #1 of the night).
Here are things I have tried and the challenges I have faced thus far:
1) CWM. Have not been able to access it or install it successfully. However have somehow managed to root the device. I did it through a one-click root/CWM tool I found online but have never been able to access CWM from the recovery screen, only stock recovery.
2) Changing the radio baseband version. Fail, since I have no CWM. Or Root Explorer because...
3) I can't access the google Market as I have no data connection. And did I mention no wireless? I live out in a rural area (sad story #1). It's ethernet only, sadly
4) Also, I have very limited access to a PC. I do have one at work, but I have my own macbook. Although I could use the PC at work to try some stuff out, I can't be spending my entire day Googling for help. Seems like employers would frown greatly on it. I've already spent a solid 4 hours on the forums and Internet tonight trying to find something that works. Absolutely no dice.
5) Attempted to get back to 2.3.6. No joy. Phone won't budge from 4.0.3. and I think it has to do a huge part with no CWM.
6) Factory reset a number of times. Still stuck on 4.0.3. with no 3G connection.
7) Reset APNs to default. Still no luck. Perhaps it isn't the radio baseband after all?
8) Also tried entering and leaving airplane mode a number of times. Zero luck.
9) I have a pretty low comfort level with PCs to be honest. I am open to all instructions, as long as they are detailed and written For Dummies.
Please help. I really, truly do not know what else to do or where else to turn but the forums. I've tried everything I could think of and I'm afraid this will impact my job since I need to be in constant phone contact for work. I'm exhausted from stress and worry. I swear this will be the last time I experiment with my phone (I know I've said it before, but this time I MEAN it!)
Thank you all you kind-hearted folk out there for anything you can do to help.
first cell phone model you have and that you had changed baseband before all ... You can also try a new version of CMW in case, can also be kernel problem that uses TO in the mobile ...
So you have a nexus with barely PC access running ics minus a recovery. Good news is your in luck. You need proper tools to do the job. Easiest method is either on that Mac or at work, install the phones drivers. search Google for the fastboot binary for the operating system your using. Once the drivers are installed boot to fast boot not recovery but the screen where you choose recovery. Open a terminal on the PC and type fastboot devices. No period. Should return a serial number on the screen. Your good to go. When you download the fastboot program, put it in a folder on the PC. Also put cwm for your phone in a .img format not a .zip. That should give you a name like cwm-2.5.5.0.img. When you open the terminal, navigate to the folder with both files. After typing fastboot devices and seeing the number type fastboot flash recovery cwm-and-whatever.img
That should give you cwm.
Also you got root have you tried downloading rommanager apk from the net putting it on the sd then installing. Once it installs try to flash recovery from the app
Sent from my Galaxy Nexus using Tapatalk 2
You have to relax first lol. When you're panicky nothing gets done so calm down. Do what the guy above says. Install cwm with fast boot. First install the android sdk then get the drivers. Get fast boot file down as well. Remember that the command fastboot flash whatever varies from operating systems.
With cwm installed, do a test. Backup your efs folder , which is essentially extremely important. You would better do a nandroud backup. Then, try various radios. See if that's your issue. If not change to trying out new roms . Worse case scenario go back to your 2.3.6 rom by flashing with cwm or install cyanogen mod 7.
Best of luck
Sent from my Nexus S using Tapatalk 2
dreamsforgotten said:
So you have a nexus with barely PC access running ics minus a recovery. Good news is your in luck. You need proper tools to do the job. Easiest method is either on that Mac or at work, install the phones drivers. search Google for the fastboot binary for the operating system your using. Once the drivers are installed boot to fast boot not recovery but the screen where you choose recovery. Open a terminal on the PC and type fastboot devices. No period. Should return a serial number on the screen. Your good to go. When you download the fastboot program, put it in a folder on the PC. Also put cwm for your phone in a .img format not a .zip. That should give you a name like cwm-2.5.5.0.img. When you open the terminal, navigate to the folder with both files. After typing fastboot devices and seeing the number type fastboot flash recovery cwm-and-whatever.img
That should give you cwm.
Also you got root have you tried downloading rommanager apk from the net putting it on the sd then installing. Once it installs try to flash recovery from the app
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Follow dreamsforgotten's instructions should get you out of the problem.
And yeah, relax.
You flashed the wrong ROM. the i9020a never got 4.0.3, it went straight from 2.3.6 to 4.0.4. you flashed a ROM for the i9020/i9023. This means that you have a US modem, a problem with those in the gingerbread days is that if you toggled 3G off, you lost it.
Now, I'm not 100% sure this will fix your issue, it *will* bring you back to proper stock image for your phone. Also, keep in mind, that you are responsible for anything you do to your phone, I in no way take any responsibility.
Instructions are for windows
Start by downloading the factory image:
Factory image for your phone
(ref) https://developers.google.com/android/nexus/images
Uncompress this file, you will need the following files:
Image-sojua-imm76d.zip
bootloader-crespo-i9020xxkl1.img
radio-crespo-i9020uckj1.img
Put these all in a folder, you'll need them shortly
Now you need to connect your phone to the computer. follow this guide, part 1 ONLY:
http://forum.xda-developers.com/showthread.php?t=1007782
You should still be in the bootloader when you do the following steps, (turn phone off, press and hold the volume down, power up the phone)
Grab a copy of fastboot.exe and put it in the folder with the IMG files (PM me if you can't find one)
Now, test to make sure your phone is seen by fastboot:
Open a cmd prompt and go to the folder where the img files and fastboot are stored.
Type: fastboot devices
you should get a response like this:
C:\temp\nexus image files>fastboot devices
xxxxxxxxxxxxxxxx fastboot
(x's will be alphanumeric)
This means that fastboot can now see your device. if you get nothing, something went wrong above.. troubleshoot that.
If everything is good, start flashing:
fastboot flash bootloader bootloader-crespo-i9020xxkl1.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020uckj1.img
fastboot reboot-bootloader
fastboot -w update image-sojua-imm76d.zip
Reboot your phone and be *Very* patient with the first boot.
You should now be good.
Thanks all so very much for all the help! It was extremely helpful and really helped to get my head around things.
What I ended up doing was (for those who might be stuck in the same situation as me):
1) Wipe everything. EVERYTHING. Used fastboot into CWM to help me do that.
2) Put in Kustom Kream found here:
http://forum.xda-developers.com/showthread.php?t=1399956
3) CM9 from here:
http://download.cyanogenmod.com/?type=nightly&device=crespo
* Not super stable to be honest; I've had at least three times where my entire phone randomly shut down and went into the CM9 boot screen and was stuck there until I did a battery pull. Reinstalled each time through CWM. Hope this gets fixed soon!
I found that Kustom Kream put CWM AND rooted my phone AND had everything working in terms of radio bands, sending SMS, etc. I originally had major issues with radios but now I have KB3 although the signal is kind of weak. Maybe because I live in a relatively far out suburban area?
But this solved my problems. Good luck to anyone out there stuck where I am, I feel your pain!
I would recommend that you at least flash a radio that is designed to work with your model - ucjk. That way you won't have any issues if you toggle to 2G.
Sent from my Galaxy Nexus
some notes
rooted using Root RK29 Tab Toolkit 1.3.
reset and vol + = flash mode rock usb.
RKAndroidToolv1.37 and RKBatchToolv1.7 work for flashing.
used rock usb driver included in either of the flash
tools. when flashing several things needed done to
enable flashing and or adb. do not enable usb storage
on the device. on windows pc used the safely remove
mass storage tool. only on the removable drives that
showed in my computer after plugging in the tablet.
in RKAndroidTool or RKBatchTool use the "switch" button
to put the unit into flash mode. I used RKAndroidTool
to flash the cwm. I tried several cwms, PER5274B_CWM.zip
was only one to boot to recovery for me
(tried many including ones from developerof cwm, just
happened to find one to boot after trying
over and over). so far. succesfully made full backups of
the unit to sd card. obviously mount the ext sd in cwm
first before backing up to sd. succesfully flashed
gapps-jb-20121011-signed.zip using PER5274B_CWM.
the stock recovery tool rejected all gapps. note gapps
sometimes closes for no apperent reason with no error.
all other gapps versions i tried crash soon as i
opened them.
cwm file working so far PER5274B_CWM.zip. have only figured
out how to boot to recovery using reboot apk.
key combo is unknown to me so far. actively trying other cwms.
Other cwm's have booted to a white screen for me.
a word to the wise, make full flash backup soon as you
get cwm on. its the only way to turn back to stock as
far as i know. I cannot find a factory rom for this
unit anywhere.
downloading cm 10.1 for rk29xxboard now, will report
results!
Cheers hope this helps out someone.
well cm10 didnt work out so well. the unit is now resting with no response. I can however still flash it with rkandroidtool. the issue I am facing now is I do not have a full dump image for this unit. I am looking for one that will at least allow me to get it to boot properly to cwm lol. I can see it with rkbatchtool as well. what I would need there is the proper parameter file. pretty sure thats all I need. I did happen to make a backup with cwm but if I cant get the tablet into cwm (currently a no go) thats not going to help me. figures I have since found out how to generate a parameter file.
good news is its not dead, just not working.
I have gotten my moneys worth out of it, not only in using this tablet but also in hacking the thing passing time.
will report further updates.
Cheers!
Well its running again, after many firmwares etc. I have the stock firmware running and two others I have modded removing system Apks I didn't want and adding a few as well.
Have several cwm backups as well, a few I plan to post links to. Googleplay works to, root, cwm and busybox also.
Still trying to get hardware keys working to launch cwm at boot by editing the parameter file. It will run when I edit the file with notepad++ and flash it but then I end up in a cwm boot loop forcing me to reflash the orig parameter file to get out of it. Cold boot will get me out if I completely drain the battery otherwise nothing short of flashing it will get me out of cwm. Using notepad++ and inserting "COMBINATION_KEY: 0,6,A,7,0" right after the kernel IMG line gets the power + volume key to start cwm at boot. Then I can't get back out lol.
stinkster said:
Well its running again, after many firmwares etc. I have the stock firmware running and two others I have modded removing system Apks I didn't want and adding a few as well.
Have several cwm backups as well, a few I plan to post links to. Googleplay works to, root, cwm and busybox also.
Still trying to get hardware keys working to launch cwm at boot by editing the parameter file. It will run when I edit the file with notepad++ and flash it but then I end up in a cwm boot loop forcing me to reflash the orig parameter file to get out of it. Cold boot will get me out if I completely drain the battery otherwise nothing short of flashing it will get me out of cwm. Using notepad++ and inserting "COMBINATION_KEY: 0,6,A,7,0" right after the kernel IMG line gets the power + volume key to start cwm at boot. Then I can't get back out lol.
Click to expand...
Click to collapse
Stinkster,
Have you made any other progress? Got my kids couple LT7035-F tablets.
Thanks
To the both of you... LT7035-J
curtisint has firmware for model lt7035-j; however, when using rkbatchtool it fails at 97%. My tab is only able to connect to the pc as of now. I can see it with batchtool; however, have not found a firmware.img file to flash to it that completes and works. Very interested in the parameters file you speak of in your second post. Don't know what you know now but I was able to get it root with a tool I found on the net. I think I have it somewhere. Well anyway I was trying to reflash stock firmware because I had no sound just a popping noise/key tone which was silent only when mute. If anyone could help out with a firmware.img that will work for me that would be great.
stink you sound like you know what you are talking about, do u java develop or something?
Hello. I've normally always been able to get myself out of a brick situation but this time I cannot figure it out. I recently rooted my G2 and attempted to remove the USB debugging icon notification by editing build.prop and adding "persist.adb.notify=0" with the build prop editor application downloaded in the app store. Once I rebooted the phone, it would not boot past the LG logo. I have the stock rom, stock kernel, on 4.2.2. I'd like to unbrick it without losing any data, if possible. I attempted to ADB into the phone and fix but this is what happened with that: I can ADB into the phone, but when trying to replace the build.prop with another, I get a operation not permitted error. So when I try to do adb shell, su it just sits there blank and doesn't do anything. No $ or #, just a blank line and never goes anywhere, so I can't get root access to mount the filesystem. Does any of any suggestions at all? I don't have any aftermarket recovery on it.
I believe you can adb pull the build.prop, edit it, and then adb push it back.
Sent from my AT&T LG G2 using Tapatalk
---------- Post added at 10:03 AM ---------- Previous post was at 10:02 AM ----------
Oops I didn't read that you said you don't have any custom recovery, thay would of been your best bet. Install custom recovery and adb pull/push
Sent from my AT&T LG G2 using Tapatalk
Well here's how I ended up fixing it, and anyone who bricks their phone in a similar way should read this.
I was able to get into download mode, so I downloaded the firmware for my phone (LG G2 D800) from this site (downloaded OCT 2013 version):
http://storagecow.eu/index.php?dir=Xda/LG+G2/Stock/AT&T/
I then used the program "LG FlashTool" to flash that firmware back onto the phone and I was instantly unbricked. The program needs to be cracked in order to use it and there is a tutorial and .zip file of the full program floating around. I will not post the link since it is a cracked program, but it's fairly easy to find. It requires putting the phone into download mode and then setting the phone in device manager to use COM port 41.
That's basically it. However, once I successfully reflashed the stock firmware, I then installed a custom recovery (TWRP). After I installed that recovery, my phone decided to automatically do a software update (f*ck!). I was now bricked AGAIN. This time, the phone wouldn't go into download mode, and I was getting an error on boot "Secure Booting Error! Cause : boot certification verify." I couldn't flash with the previous tool because I couldn't get into download mode, and I couldn't use TWRP because unfortunately for me, the touch wasn't working so I couldn't navigate to any menus. The phone was also not showing up in device manager as a COM serial object, so LG FlashTool was a no go this time. I could however ADB into the phone and fastboot, but nothing I did seemed to work in either. I tried flashing different recoveries, but that just put me into fastboot loop, or didn't work at all. At the end of the day, I finally found out that simply replacing the following boot image files with the one's that match your firmware (10d or 10o), the phone finally booted up and I jumped for joy. Here are the file names, and where to get them: aboot.img, boot.img, rpm.img, tz.img, laf.img, sbl1.img, recovery.img.
These images can be downloaded here. http://downloads.codefi.re/autoprime/LG/LG_G2/D800/Stock_Firmware
I then followed Partager.info's guide to copying the files over (http://forum.xda-developers.com/showthread.php?t=2582142).
Basically, you have to figure out which partitions the images reside on your phone. In my case, using the guide above, I found that these were my partitions setups:
sbl1.imb - 2
aboot.img - 5
rpm.img - 6
boot.img - 7
tz.img - 8
recovery.img - 15
If you're using his guide and are in linux, you can simply follow it to replace the files. After I replaced all the mentioned image files, I rebooted the phone and got an android icon saying software updating, but it got an error after about 12% and rebooted. Then it rebooted into the OS and I was unbricked AGAIN. This was a HUGE hassle and I spent so many hours figuring this out. If this has happened to you or something similar, shoot me an email at [email protected] and I'll try to help you out with whatever I can.
djpelosi said:
Well here's how I ended up fixing it, and anyone who bricks their phone in a similar way should read this.
I was able to get into download mode, so I downloaded the firmware for my phone (LG G2 D800) from this site (downloaded OCT 2013 version):
http://storagecow.eu/index.php?dir=Xda/LG+G2/Stock/AT&T/
I then used the program "LG FlashTool" to flash that firmware back onto the phone and I was instantly unbricked. The program needs to be cracked in order to use it and there is a tutorial and .zip file of the full program floating around. I will not post the link since it is a cracked program, but it's fairly easy to find. It requires putting the phone into download mode and then setting the phone in device manager to use COM port 41.
That's basically it. However, once I successfully reflashed the stock firmware, I then installed a custom recovery (TWRP). After I installed that recovery, my phone decided to automatically do a software update (f*ck!). I was now bricked AGAIN. This time, the phone wouldn't go into download mode, and I was getting an error on boot "Secure Booting Error! Cause : boot certification verify." I couldn't flash with the previous tool because I couldn't get into download mode, and I couldn't use TWRP because unfortunately for me, the touch wasn't working so I couldn't navigate to any menus. The phone was also not showing up in device manager as a COM serial object, so LG FlashTool was a no go this time. I could however ADB into the phone and fastboot, but nothing I did seemed to work in either. I tried flashing different recoveries, but that just put me into fastboot loop, or didn't work at all. At the end of the day, I finally found out that simply replacing the following boot image files with the one's that match your firmware (10d or 10o), the phone finally booted up and I jumped for joy. Here are the file names, and where to get them: aboot.img, boot.img, rpm.img, tz.img, laf.img, sbl1.img, recovery.img.
These images can be downloaded here. http://downloads.codefi.re/autoprime/LG/LG_G2/D800/Stock_Firmware
I then followed Partager.info's guide to copying the files over (http://forum.xda-developers.com/showthread.php?t=2582142).
Basically, you have to figure out which partitions the images reside on your phone. In my case, using the guide above, I found that these were my partitions setups:
sbl1.imb - 2
aboot.img - 5
rpm.img - 6
boot.img - 7
tz.img - 8
recovery.img - 15
If you're using his guide and are in linux, you can simply follow it to replace the files. After I replaced all the mentioned image files, I rebooted the phone and got an android icon saying software updating, but it got an error after about 12% and rebooted. Then it rebooted into the OS and I was unbricked AGAIN. This was a HUGE hassle and I spent so many hours figuring this out. If this has happened to you or something similar, shoot me an email at [email protected] and I'll try to help you out with whatever I can.
Click to expand...
Click to collapse
Hi , sorry to bother you, I have a D806 to install a rom kdz vs980 . Now I can not go back to the stock rom D806 .
you think your post might help me?
I'm desperate
I'm going to try and encapsulate everything that's going on into this initial thread but I'm sure I'll miss something.
Basically, I undertook to root my phone last night. I followed all the steps in the root thread, and I thought it worked, but then when I went to the root checker to see if I was successful. The test couldn't get a result the first time, and then failed the second time. I've known my phone to be a little temperamental when it comes to stuff like that, so I shrugged it off. Then, everything started running with so much lag that my only option was a reboot. It came back up just fine, but then, apps wouldn't open anymore. Since a reboot fixes everything, I rebooted AGAIN... except no I didn't, because I couldn't move past the white splash screen.
After some time hacking around with TWRP, system restoring my phone and the like, I finally managed to actually load the OS again. I think the phone was rooted at that time, but I don't know for sure, because this was the drawback: I couldn't install ANYTHING. My idea is that the system was rebooted into read-only mode. I tried everything I could think of to revert the system to rewriteable again, but nothing ever panned out. There was just one thing that stood out to me: "Your phone worked properly when it wasn't rooted." So, I got the brilliant idea to use SuperSU to unroot my phone. Stupid, stupid move, because now my phone can't boot past the white splash screen again. As a last ditch effort, I decided that it was time to flash the stock system to the phone. Except I probably did it wrong.
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash recovery system.img
Code:
fastboot flash recovery boot.img
And where I stand now is that my phone will not boot past the white splash screen, and I can no longer access either TWRP or Fastboot.
Is my phone fooked, or can anyone save this?
#1 You can't flash system image via fastboot - it's semi-locked.
#2 You can't use 'flash recovery' command for boot and system images.
#3 For restoring your phone use SP Flash Tool - there's a thread in the General section called 'How to unbrick'.
Try it and let us know.
Cheers
Yeah, I realized afterward that if I were trying to flash the image of the system, I should not have used the "flash recovery" command because I disabled access to the other recoveries, lol. I have tried to use the SP Flash Tool in the past few days, but I could never get any download progress. I think my computer isn't making the VCOM drivers accessible to be able to flash those things to my phone. Do you have any advice on that end? Because I have seen that thread and tried those steps but I'm just not successful.
You should also read all replies to this thread - there are people who solved their problems with SPFT in their own way, that's how I've revived my phone from hardbrick.
Make sure you're phone is disconnected when you start the flash. AFTER you hit the download button in SPFT... then connect your phone...
Fantastic advice from both of you. I'm ready to revive my phone!
Okay, I think I'm making good progress on recovering my phone. I have managed to get back the stock recovery onto my phone, which I then used to install TWRP. But I'm not out of the woods yet. I used fastboot to flash the boot image onto my phone also, but when it came to the system image, I'm having a lot of trouble. The only ROM I can find for the Blu Pure XL is a 7z file. Now, I know how those work, I have 7zip and I extracted it for the system image. When fastboot was available to me, I couldn't push the system image to the phone. Now that I have TWRP and I have no more access to fastboot, I've tried to load the system file onto my phone through my SD card in four different ways:
As a .img file
As a .7z file
As a .zip file that I created by zipping up the image file
As a .zip file that was .7z, but I changed the extension
None of those methods worked. The Blu development thread doesn't point me to a zipped ROM file. One person there said that they had a backup of their files and provided a link, but those images seem to have been removed.
I'm so close, I can see this phone working again in the near future, I just need your help to get me there. Please! :'(
Edit: Also, keep in mind, I'm dumb. I don't think I really did anything super wrong, but I may be missing something ultra obvious. So if you could just keep your answers dumb for me, it would help even more.
I would stop trying to use all of the methods you are using I believe you are slightly confused by them at this time..
At this point what you have done with the random image flashing is get damaged partitions..
Get SPFT. Turn off you phone completely.
Download the full Scatter file for you phone. (put it aside).
Download a file called ALL MTK driver install. ( or something to that effect). Search for it on Google. You will find it. Run it and then reboot your PC completely.. (if you have windows 8 or higher look online on how to install unsigned drivers) --THIS IS THR BIGGEST PROBLEM PEOPLE HAVE--
Extract your full downloaded scatter image to a directory.. (you can download the Gionee E8 image if you want) it is what I am running on my Blu..
Run SPFD read the thread that they pointed out to you. Find the scatter and point SPFD.. Once it is loaded on the program UNCHECK the PRELOADER check box.. (if not you can cause problems) ..
click download and after 10 seconds or so plug in (you completely powered off) phone into the computer..
.Then wait..... and wait... It will tell you it's progress..
Keep trying it, it WILL work.. and ALWAYS unchecked preloaded when flashing with spdf...
I did follow all the steps in the original guide, and I followed the steps that you gave me too, down to using the advanced device manager to remove any MediaTek drivers from the computer and restarting the computer with disabling the driver signature verification, but when I click download, wait, and plug my phone into the computer, just nothing happens. The computer says it's an unrecognized device, and the download never progresses.
I see also that you said keep trying, but every time I try the SPFT, it never sends anything to my phone. And I don't even know how to tell if I'm missing some important step.
OK this happens sometimes. plug the phone in with device manager open.. plug the phone in when it is off..
When it says unrecognized device double click on it really fast( it will disappear fast, try it a couple of times if you don't get it the first time) then hit update driver.. point it to the MTK drivers folder (unzip the MTK drivers folder). It will pick the proper driver. on some computers it loads up so fast it has no time to recognize the driver..
After you load the drivers power off your phone again and follow the instruction I gave.. After you do this once it will load the drivers right after this..
When I double click on the unrecognized device button, it just brings up a notification that my device wasn't recognized because it malfunctioned. I don't have an option to install any drivers.
My problem is finally solved. After starting up SPFT and clicking download, I held Vol - and Power and then connected it, and that pushed the download forward. I got to the Blu animation screen, and it stayed up FOREVER, but then the next time I looked over, it was on the initial setup screen. Good as new.
Thank you guys for all your help. This forum really is an amazing place.
If I'd prefer not to purchase a new phone, is there much risk a rootkit is installed? Or, is this certainly random device corruption that doesn't seem to be harming anything?
Is there anything I can do to fix the problem? (Yes, I could turn dm-verity off through adb, but that hides the error without fixing it.)
TL;DR
I have an Asus Zenfone V Verizon edition, which is the V520KL A006.
When I was using my phone a few days ago, it suddenly rebooted and since then shows:
Your device is corrupt. It can't be
trusted and may not work properly.
Visit this link on another device:
g.co/ABH
If power key is not pressed:
Your device will poweroff in 30 seconds
Click to expand...
Click to collapse
Fastboot shows:
TARGET PROJECT : V520KL
IMAGE VERSION : V5.6.0
BUILD VARIANT : USER
SECURE BOOT : enabled
DEVICE STATE : locked
Software status : Official
Click to expand...
Click to collapse
After a few days, I finally tried the power button, and it boots up just fine, and seems perfectly stable. I performed complete backups, and for what it's worth, I ran a bunch of droid virus/malware/rootkit scanners, and they found nothing. (Obviously, a good rootkit will hide itself.)
I eventually did a factory reset. This went well, but the red error message remains. So, I believe the corruption must be in a partition that a reset doesn't replace.
MORE DETAILS
I've never unlocked, rooted, or installed a custom ROM onto this phone. The only "beyond typical user" thing I'd previously done is to install adb sourced directly from Google, to be able to run Genymobile's scrcpy, which is an extremely fast open source program that allows me to remotely control my phone from my linux PC, via USB or wireless. I've been using this for many months without any issues.
This appears to mean dm-verity is detecting corruption, and is the "red" version of it which many have described as the death of their device. I believe this means the phone is able to verify the signature on the bootloader and it's able to verify the signature on the kernel, but that the kernel is finding an invalid block(s) on one of the many partitions being read right at turning on (detected because the hash for the block is not as expected.) When this happens, an I/O error is given indicating the block cannot be read.
I have been quite concerned if this might indicate a rootkit had been installed. I haven't done anything that I would suspect could let one in. After spending a lot of time learning about adb, fastboot, TWRP, and having the ultimate goal of discovering which partition has an unexpected hash, determining if this meant a rootkit or file corruption, and fixing the error, I've hit many brick walls.
For a day or two, I avoided seeing if the power button would allow it to boot, because if there was a rootkit, I didn't want it to run. I was disappointed to learn that through fastboot (specifically, I mean the fastboot PC program that connects to the droid when in fastboot mode), there is no way to do something like a full bitwise image of the internal storage, and analyze the situation in linux. Or, any type of backup whatsoever. I was frustrated to learn from another XDA thread about a lot of problems others have had rooting and/or installing TWRP on this device. I was frustrated to see there is no prebuilt version of TWRP for my device. (There is an image for the Asus ZenFone 5z 2018 ZS620KL which is very different than my Zenfone V520KL V.)
I realized with my particular device, I think, the only way I was going to take any next step required hitting the power button. (As I mentioned way above, that's when I found it appears to work fine, and I eventually did a factory reset.)
I attempted using the TWRP recovery.img posted by game #1 in that XDA thread about my device, but like he encountered, fastboot boot recovery.img doesn't work, and just reboots instead.
Without being able to extract the original recovery.img, I'm not sure that I'm willing to install his and see if it works for me. I was frustrated to find there appears to be no way to extract the original recovery.img without first having root access. All non-root methods I later found to do this didn't work. Notably, su can't run anymore through adb, and adb root can't run with a user build.
I've looked a bit at custom compiling TWRP myself, but haven't done that yet. In part, because if my version doesn't work through fastboot boot recovery.img, I'd have the same concern about overwriting the original one before getting some feedback here. Also in part, because I haven't looked enough to find how someone goes about making a BoardConfig.mk and the device tree from scratch.
Hey. I tried installing TRWP on my device, Asus Zenfone 5Z (ZS620KL) but I also got the same message. "This phone is corrupted and cannot be trusted." It also said it won't boot. Now I am stuck in Fastboot mode.
I tried installing a stock rom. Downloaded the firmware. i even downloaded python so I can extract the payload.bin file. Followed the steps but still to no avail.
Is there anyone who could help me?
If you could attach the files that I would be needing, that would be a great help.
Thanks.