Related
Hey guys, this is my first post on XDA forum.
So I've recently bought a nexus 7, I used wugfresh's root kit to root my nexus but then it didn't work... so I've tired the auto root by chainfire. Then I was able to get root. So then I went to playstore and downloaded rom manager to install CWM. I went to recovery then I get this message:
E : Cant mount /cache/recovery/log etc.....
I've tried everything I can do such as researching, changing recovery, and watching a youtube tutorial but nothing helped.
Thanks.
I would start over from scratch using fastboot to flash a factory image and stock recovery. If your bootloader isn't unlocked already, unlock it.
nhizzat said:
I would start over from scratch using fastboot to flash a factory image and stock recovery. If your bootloader isn't unlocked already, unlock it.
Click to expand...
Click to collapse
I tried to format using wugfresh couple times but still not working...
DO NOT USE TOOLKITS. They cause too many problems. Learn to do things the proper way using fastboot. I agree with the poster above, you should flash a factory image to start over. Download the system image from here- https://developers.google.com/android/nexus/images
You need to unlock your bootloader-
Code:
fastboot OEM unlock
Then run the flash_all.bat. That will automatically wipe and reflash everything to get you back to square one.
Then you need to flash TWRP (don't use CWM)
Code:
fastboot flash recovery recoveryname.img
TWRP will automatically prompt you to flash SU when you reboot. Choose yes, reboot, then install SuperSU from play store, update the SU binaries, reboot again, and then you're done.
_MetalHead_ said:
DO NOT USE TOOLKITS. They cause too many problems. Learn to do things the proper way using fastboot. I agree with the poster above, you should flash a factory image to start over. Download the system image from here- Link Removed
You need to unlock your bootloader-
Code:
fastboot OEM unlock
Then run the flash_all.bat. That will automatically wipe and reflash everything to get you back to square one.
Then you need to flash TWRP (don't use CWM)
Code:
fastboot flash recovery recoveryname.img
TWRP will automatically prompt you to flash SU when you reboot. Choose yes, reboot, then install SuperSU from play store, update the SU binaries, reboot again, and then you're done.
Click to expand...
Click to collapse
I tried to flash TWRP but its still the same error code
z3r0c311 said:
I tried to flash TWRP but its still the same error code
Click to expand...
Click to collapse
I highly advise you start from scratch so do what I told you to do in my last post. I promise if you do it the correct way (ie. without using toolkits) it will work.
_MetalHead_ said:
I highly advise you start from scratch so do what I told you to do in my last post. I promise if you do it the correct way (ie. without using toolkits) it will work.
Click to expand...
Click to collapse
It would be great if u could tell me the commands, im nubby with this fastboot thing.
z3r0c311 said:
It would be great if u could tell me the commands, im nubby with this fastboot thing.
Click to expand...
Click to collapse
I gave you the commands in my first post in this thread.
Here's a guide to get you started-
http://forum.xda-developers.com/showthread.php?t=2277112
Sorry for another nubby question but how do I get flash_all.bat?
z3r0c311 said:
Sorry for another nubby question but how do I get flash_all.bat?
Click to expand...
Click to collapse
It's in the file that you should have downloaded from the link I posted in my first post. The instructions are at that link as well.
_MetalHead_ said:
It's in the file that you should have downloaded from the link I posted in my first post. The instructions are at that link as well.
Click to expand...
Click to collapse
Hey I tried the following:
oem lock
oem unlock
flash-all/flash_all.bat
flash recovery(TWRP)
but then when I reboot into TWRP I don't get a message saying you to install SU... And when I go to 'Install' in TWRP I don't see any internal storage available(0mb). With this error I cant install any roms which is boring.
z3r0c311 said:
Hey I tried the following:
oem lock
oem unlock
flash-all/flash_all.bat
flash recovery(TWRP)
but then when I reboot into TWRP I don't get a message saying you to install SU... And when I go to 'Install' in TWRP I don't see any internal storage available(0mb). With this error I cant install any roms which is boring.
Click to expand...
Click to collapse
Hmm... Can you even boot into the stock ROM at this point? Try formatting /data (done in TWRP). Did the system image flash successfully?
_MetalHead_ said:
Hmm... Can you even boot into the stock ROM at this point? Try formatting /data (done in TWRP). Did the system image flash successfully?
Click to expand...
Click to collapse
I can boot into my stock rom which is 5.0.2, when I try to format /data the error codes comes out...
z3r0c311 said:
I can boot into my stock rom which is 5.0.2, when I try to format /data the error codes comes out...
Click to expand...
Click to collapse
Did the system image flash successfully?
_MetalHead_ said:
Did the system image flash successfully?
Click to expand...
Click to collapse
using flash-all command, yeah
z3r0c311 said:
using flash-all command, yeah
Click to expand...
Click to collapse
Well then I don't know what to tell you at this point. I know Lollipop has been causing issues for some N7 users, but I also know that wugs toolkit causes problems too so honestly I'm not sure what the root of your issue is. I think someone with more experience with Lollipop is gonna have to chime in here, I'm still on 4.4.4 on all of my devices. Sorry I couldn't be of more help.
_MetalHead_ said:
Well then I don't know what to tell you at this point. I know Lollipop has been causing issues for some N7 users, but I also know that wugs toolkit causes problems too so honestly I'm not sure what the root of your issue is. I think someone with more experience with Lollipop is gonna have to chime in here, I'm still on 4.4.4 on all of my devices. Sorry I couldn't be of more help.
Click to expand...
Click to collapse
Thanks for helping me I appreciate it. I hope someone else can help me with this problem... btw can I flash roms with the stock recovery? The stock recovery seems to be working fine...
z3r0c311 said:
Thanks for helping me I appreciate it. I hope someone else can help me with this problem... btw can I flash roms with the stock recovery? The stock recovery seems to be working fine...
Click to expand...
Click to collapse
No, you can only flash custom ROMs if you have a custom recovery.
I was on cm 13 something and flashed cm 14.1 everything was working ok but i didnt flashed gapps zip.
so i tried to go into recovery and there was no recovery anymore...
then i reset cm 14.1 that i can start from a fresh rom and since then i cant start my phone
i dont have a recovery i can get in but i can get into fastboot mode
hope someone is able to help me and could tell me what to do / try to install a working system again
Inlacrimas said:
I was on cm 13 something and flashed cm 14.1 everything was working ok but i didnt flashed gapps zip.
so i tried to go into recovery and there was no recovery anymore...
then i reset cm 14.1 that i can start from a fresh rom and since then i cant start my phone
i dont have a recovery i can get in but i can get into fastboot mode
hope someone is able to help me and could tell me what to do / try to install a working system again
Click to expand...
Click to collapse
Use this toolkit on a pc to fix your recovery, forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Hope it helps.
JoshDaWhite said:
Use this toolkit on a pc to fix your recovery, forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Hope it helps.
Click to expand...
Click to collapse
i am not that familir with all these kinds of stuff
what would be the steps i had to do ?
Inlacrimas said:
i am not that familir with all these kinds of stuff
what would be the steps i had to do ?
Click to expand...
Click to collapse
Download the toolkit and unzip it. Launch the bat file and the find the option to flash twrp recovery.
JoshDaWhite said:
Download the toolkit and unzip it. Launch the bat file and the find the option to flash twrp recovery.
Click to expand...
Click to collapse
it doesnt find my device
when i press 7 it tells me error device not found
Inlacrimas said:
it doesnt find my device
when i press 7 it tells me error device not found
Click to expand...
Click to collapse
Enter fastboot mode. Connect device to pc. You need to download the attached zip. Unzip it, open the folder until you see a bunch of files.Click the back button, select the folder, press Shift and click the right side of the mouse, and select open command window here.use the command fastboot devices and report back.
This is the zip I told you about.
JoshDaWhite said:
This is the zip I told you about.
Click to expand...
Click to collapse
nothing happend to the phone stays in fastboot
Inlacrimas said:
nothing happend to the phone stays in fastboot
Click to expand...
Click to collapse
Yes but the command returned any results?
JoshDaWhite said:
Yes but the command returned any results?
Click to expand...
Click to collapse
yes 9771bc7e fastboot like in the linked picture
Inlacrimas said:
yes 9771bc7e fastboot like in the linked picture
Click to expand...
Click to collapse
Unfortunately the picture is too small to read from it. It is great! It means your device can receive fastboot commands! I can guide you how to install stock Oxygen os 3.2.7. That also means you lose your data from internal storage. Do you want Oxygen os 3.2.7?
JoshDaWhite said:
Unfortunately the picture is too small to read from it. It is great! It means your device can receive fastboot commands! I can guide you how to install stock Oxygen os 3.2.7. That also means you lose your data from internal storage. Do you want Oxygen os 3.2.7?
Click to expand...
Click to collapse
i want any system that works currently since i cant get into recovery ^^
if i can go back into recovery i should be able to manage stuff on my own or i just flash rom xyz afterwards then thats no big deal
you can click on the magnifying glass to make it bigger :good:
JoshDaWhite said:
Unfortunately the picture is too small to read from it. It is great! It means your device can receive fastboot commands! I can guide you how to install stock Oxygen os 3.2.7. That also means you lose your data from internal storage. Do you want Oxygen os 3.2.7?
Click to expand...
Click to collapse
i tried arround and managed to flash twpr with the programm but nothing has changed cant boot into recovery
Inlacrimas said:
i tried arround and managed to flash twpr with the programm but nothing has changed cant boot into recovery
Click to expand...
Click to collapse
Flash the stock recovery then sideload Oxygen os.
JoshDaWhite said:
Flash the stock recovery then sideload Oxygen os.
Click to expand...
Click to collapse
tried flashing stock recovery phone powers of or rebbots or something
how can i sideload theoxygen os ?
Think i just helped myself with
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
works again thanks for your help
Inlacrimas said:
tried flashing stock recovery phone powers of or rebbots or something
how can i sideload theoxygen os ?
Think i just helped myself with
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
works again thanks for your help
Click to expand...
Click to collapse
Glad you fixed it.
JoshDaWhite said:
Glad you fixed it.
Click to expand...
Click to collapse
Really appreciate all the time you spent helping here :good:
Inlacrimas said:
I was on cm 13 something and flashed cm 14.1 everything was working ok but i didnt flashed gapps zip.
so i tried to go into recovery and there was no recovery anymore...
then i reset cm 14.1 that i can start from a fresh rom and since then i cant start my phone
i dont have a recovery i can get in but i can get into fastboot mode
hope someone is able to help me and could tell me what to do / try to install a working system again
Click to expand...
Click to collapse
Fyi, if u decide to go back to 14.1, you will need to flash modified twrp http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Then recovery will stay intact
I was on nougat on my L21_hw_eu before i tried to upgrade manualy to oreo. i tried the twrp and terminal method and my phone started upgading. It failed at 72% saying "update verification failed". I lost my stock rom and bricked my phone.
Then i manualy flashed different Update.app images and was able to unbrick my phone .
I tried lineage OS and stock oreo.
Problems are:
1: I cant factory reset my phone using stock recovery it fails at 24%
2: FingerPrint Sensor won't work except for gestures (in Stock oreo. works in LineageOs)
3: Themes dont work
4: Flash light don't work
4: CAMERA is not responding. in both roms
in lineageOs everything works perfectly except Camera.
Please provide me details for what am i doing wrong..
iu.khan53 said:
I was on nougat on my L21_hw_eu before i tried to upgrade manualy to oreo. i tried the twrp and terminal method and my phone started upgading. It failed at 72% saying "update verification failed". I lost my stock rom and bricked my phone.
Then i manualy flashed different Update.app images and was able to unbrick my phone .
I tried lineage OS and stock oreo.
Problems are:
1: I cant factory reset my phone using stock recovery it fails at 24%
2: FingerPrint Sensor won't work except for gestures (in Stock oreo. works in LineageOs)
3: Themes dont work
4: Flash light don't work
4: CAMERA is not responding. in both roms
in lineageOs everything works perfectly except Camera.
Please provide me details for what am i doing wrong..
Click to expand...
Click to collapse
If you only have extracted images flashed from update.app, then you do not have the full rom installed.
You should run either hurupdater of HWOTA again to get full emui8 installed.
mrmazak said:
If you only have extracted images flashed from update.app, then you do not have the full rom installed.
You should run either hurupdater of HWOTA again to get full emui8 installed.
Click to expand...
Click to collapse
I suspected that too...
Now my TWRP hangs at initial screen. i m using p20lite.img twrp
other TWRP works but they dont have adb enabled
is there a way i could flash through fastboot?
iu.khan53 said:
I suspected that too...
Now my TWRP hangs at initial screen. i m using p20lite.img twrp
other TWRP works but they dont have adb enabled
is there a way i could flash through fastboot?
Click to expand...
Click to collapse
no,
dont adb though.
mrmazak said:
no,
dont adb though.
Click to expand...
Click to collapse
HuRUpdater keeps loading on initial screen and
HWota Fails after installing no check recovery.
screenshot attached..
iu.khan53 said:
HuRUpdater keeps loading on initial screen and
HWota Fails after installing no check recovery.
screenshot attached..
Click to expand...
Click to collapse
Is that v3.1 . I pulled that version because of error 2 messages.
Check the guide and download again. File name should be. ...
NVM, I just put the download link here.
https://www.androidfilehost.com/?fid=746163614322268008
mrmazak said:
Is that v3.1 . I pulled that version because of error 2 messages.
Check the guide and download again. File name should be. ...
NVM, I just put the download link here.
https://www.androidfilehost.com/?fid=746163614322268008
Click to expand...
Click to collapse
Hwota was successful with the newer version but after rebooting update failed at 0%
iu.khan53 said:
Hwota was successful with the newer version but after rebooting update failed at 0%
Click to expand...
Click to collapse
Please screenshot the twrp screen before reboot.
mrmazak said:
Please screenshot the twrp screen before reboot.
Click to expand...
Click to collapse
i flashed different images from UPDATE.APP manually through fastboot and twrp.. I was succesfull and fingerprint was working but camera was still not working so i stupidity flashed DTS.IMG, ODM.img, and ERECOVERY_KERNEL.img through twrp and when i rebooted. there was completely black screen and nothing was working. fastboot only recognizes device and i m able to send commands . i wanted to flash other dts,odm and ERECOVERY_KERNEL.img through fastboot but it says "remote command not allowed". there is absolutely no life in phone. i think it is hard bricked. is there a way to get device back?? or else i m completely F****D.
iu.khan53 said:
i flashed different images from UPDATE.APP manually through fastboot and twrp.. I was succesfull and fingerprint was working but camera was still not working so i stupidity flashed DTS.IMG, ODM.img, and ERECOVERY_KERNEL.img through twrp and when i rebooted. there was completely black screen and nothing was working. fastboot only recognizes device and i m able to send commands . i wanted to flash other dts,odm and ERECOVERY_KERNEL.img through fastboot but it says "remote command not allowed". there is absolutely no life in phone. i think it is hard bricked. is there a way to get device back?? or else i m completely F****D.
Click to expand...
Click to collapse
You are well past anything I. Have dealt with.
mrmazak said:
You are well past anything I. Have dealt with.
Click to expand...
Click to collapse
well i will try to repair it with sigma device. I heard it can flash anything on to device through fastboot. I will try that otherwise i have to give it to huawei service centre and pray they accept to repair it.
iu.khan53 said:
well i will try to repair it with sigma device. I heard it can flash anything on to device through fastboot. I will try that otherwise i have to give it to huawei service centre and pray they accept to repair it.
Click to expand...
Click to collapse
can not explain it, but I have seen that camra not working problem, and the blank black screenfixed by flashing the vendor partiton. The bad part about that is, i do not think it flashes with fastboot.
mrmazak said:
can not explain it, but I have seen that camra not working problem, and the blank black screenfixed by flashing the vendor partiton. The bad part about that is, i do not think it flashes with fastboot.
Click to expand...
Click to collapse
i took the phone to local repair shop they flashed naugat on it and were unsuccesfull(naugat cant be flashed on oreo) but i am again at fastboot with situation similar to this thread.
https://forum.xda-developers.com/mate-9/help/please-help-bootloop-error-func-14-1-t3724685
iu.khan53 said:
i took the phone to local repair shop they flashed naugat on it and were unsuccesfull(naugat cant be flashed on oreo) but i am again at fastboot with situation similar to this thread.
https://forum.xda-developers.com/mate-9/help/please-help-bootloop-error-func-14-1-t3724685
Click to expand...
Click to collapse
As far as I know (which is not that far). You need three images to be correct for recovery to load on oreo based device.
1. recovery_ramdisk.img
2. kernel.img
3. recovery_vbmeta
try to flash those in fastboot first. and see if they complete without error.
then if they do flash, try to boot into recovery. (try with stock first-- can try TWRP after if this works)
mrmazak said:
As far as I know (which is not that far). You need three images to be correct for recovery to load on oreo based device.
1. recovery_ramdisk.img
2. kernel.img
3. recovery_vbmeta
try to flash those in fastboot first. and see if they complete without error.
then if they do flash, try to boot into recovery. (try with stock first-- can try TWRP after if this works)
Click to expand...
Click to collapse
i cant flash ramdisk images. ithink i m on naugat now because i am able to flash succesfully recovery.img and boot.img in recovery and boot partitions. but cant flash ramdisk and kernel.
and what is iom3 image. error do i need to flash something for that?
and also hifi image error when upgrading through dload method
iu.khan53 said:
i cant flash ramdisk images. ithink i m on naugat now because i am able to flash succesfully recovery.img and boot.img in recovery and boot partitions. but cant flash ramdisk and kernel.
and what is iom3 image. error do i need to flash something for that?
and also hifi image error when upgrading through dload method
Click to expand...
Click to collapse
oh, well let me get together some nougat suggestions
mrmazak said:
oh, well let me get together some nougat suggestions
Click to expand...
Click to collapse
i have sent phone to the service center. waiting for their response now. They told me if they were unable to repair the phone then i will get a new one. lets hope for the best.
iu.khan53 said:
i have sent phone to the service center. waiting for their response now. They told me if they were unable to repair the phone then i will get a new one. lets hope for the best.
Click to expand...
Click to collapse
That sounds good
mrmazak said:
That sounds good
Click to expand...
Click to collapse
Received call today they were unable to repair it. They said they will get me a new one as soon as new stock arrives.
mrmazak said:
That sounds good
Click to expand...
Click to collapse
Recieved new phone today. Works like a charm. but again stuck on naugat. i will wait for official upgrade this time
Edit:
Got upgrade to oreo today. Love the new UI.
I was buy this phone a few days ago with ubl already. I think that was great because i don't need to unlock the bootloader by myself. Since this my first xiaomi phone, unlocking the bootloader may gave me headache. But when i tried to flash twrp, i face a problem that adb said "FAILED (remote: Requested download size is more than max allowed)". At the same time, in fastboot screen shown "press anykey to shutdown". Is somebody here know what must i do? I was spend at least six days looking for solution on internet.. but, still no luck. Hope someone here will help. Any suggestions will so appreciated.
-Sorry for my bad English
Additional info:
On me, isn't driver or port or my windows 10 problem like some people saying since i can run any fastboot commands (flashing twrp too) with another xiaomi phone.
Check this thread
https://forum.xda-developers.com/re...uide-fix-locking-bootloader-fake-ubl-t3833631
deathbearer said:
Check this thread
https://forum.xda-developers.com/re...uide-fix-locking-bootloader-fake-ubl-t3833631
Click to expand...
Click to collapse
Sorry for late replying.. Actually, i though fake UBL is not the problem since my device can bind mi account. I do research for 2 weeks and find nothing can solved this problem
Kratos-mgc said:
Sorry for late replying.. Actually, i though fake UBL is not the problem since my device can bind mi account. I do research for 2 weeks and find nothing can solved this problem
Click to expand...
Click to collapse
Get this zip : https://files.orangefox.website/OrangeFox-Stable/whyred/
Extract it.. find recovery.img and put it in your fastboot folder, run 'fastboot boot recovery.img'.. now, after going to recovery the device will show up as storage in Windows, and put the orange fox zip in internel memory and flash it with booted recovery....
DKWxda said:
Get this zip : https://files.orangefox.website/OrangeFox-Stable/whyred/
Extract it.. find recovery.img and put it in your fastboot folder, run 'fastboot boot recovery.img'.. now, after going to recovery the device will show up as storage in Windows, and put the orange fox zip in internel memory and flash it with booted recovery....
Click to expand...
Click to collapse
Thanks.. Downloading file right now. I thought i've done that before with older version of OrangeFox without luck. Have try with Official TWRP and RedWolf too with same result. But, will try with latest version like you said :highfive:
Kratos-mgc said:
Thanks.. Downloading file right now. I thought i've done that before with older version of OrangeFox without luck. Have try with Official TWRP and RedWolf too with same result. But, will try with latest version like you said :highfive:
Click to expand...
Click to collapse
Np .. post here what happened..
DKWxda said:
Np .. post here what happened..
Click to expand...
Click to collapse
Sure
DKWxda said:
Np .. post here what happened..
Click to expand...
Click to collapse
Same as before.. fail either. What should i gonna do now?
Actually, my phone already had twrp installed with custom rom too after 2 weeks use time. I can't find solution for my problem so i do unusually step (or you can say frustrating step). Do test point things and flash rom like usual. But, before i replace stock recovery with twrp and rename it like stock one. After that, just start flashing and when it finish, boot to recovery directly and flash magisk plus no verity. Then i got twrp and root.. But, still can't flash anything from fastboot, even flashing with miflash. Just curious what exactly the problem is. I know can repeat the same step just in case i got problem to boot and somehow can't boot to twrp too. But, you know.. that takes lot of time to do
I don't know if ur problem is solved by now, i think you should flash latest dev firmware, that might be the key, have you ever done that after the problem? You should use twrp to do that tho.. and pls take note, every firmware is not supported by everry recovery, but i trust orange fox, and don't try to downgrade firmware too, check always if the cutom rom support the firmware you gonna flash and also check ARB value...
Edit: what does this mean
replace stock recovery with twrp and rename it like stock one
Im using official TWRP but the touchscreen does not work, how can i get around this?
Try to hold power button for 9-10 seconds
hogze94 said:
Im using official TWRP but the touchscreen does not work, how can i get around this?
Click to expand...
Click to collapse
same here, did you get any solution?
Same to me... help!
lupomarano said:
Same to me... help!
Click to expand...
Click to collapse
what screen do you have?
Sprut_name said:
what screen do you have?
Click to expand...
Click to collapse
I have a MI A2 lite,
reflash twrp .. i had the same issue yesterday ..
Connect the phone to the computer (fastboot mode)
Launch the command line and go to the folder where you put all the prerequisites (cd Folder_name)
Boot the recovery image: fastboot boot twrp-daisy-3.3.0-0-offain.img
You will see the recovery on your phone, prompting to enter the password. Choose "Cancel"
Click to expand...
Click to collapse
solved said:
reflash twrp .. i had the same issue yesterday ..
Click to expand...
Click to collapse
tried it over and over again. still having this issue.
TWRP loads up showing me the "Keep System Read only?" page. Touchscreen wont work.
using twrp-installer-3.3.0-dees_troy-daisy
flash a stock rom , then use offain 3.3.0-0 twrp
I have the same problem, this should help https://forum.xda-developers.com/mi-a2/how-to/guide-flashing-roms-twrp-black-screen-t3913052
Thats because u dont have OS, You need to flash OS with MiFlash, unlock bootloader and flash TWRP