Hi,
I wanted to install MultiRom on my nexus 7, so I tried
I first flashed the required zip folder, was working fine.
Then I went to flash the recovery.img
It was stuck on waiting for device, but I saw that I needed to upgrade my bootloader.
When I tried fastboot flash bootloader bootloader.img, It was stuck on waiting for device.
So, I tried the flash-able zip.
I didn't put it on internal storage, so I adb pushed it.
But, it said "error: device not found"
I tried adb devices, but same thing.
I made a backup before all this, so I'm also wondering:
Will restoring not restore my apps/setting, etc?
Also, I'm using fastboot 3.41, TWRP 2.6.0.0
*EDIT*
Okay, rebooting my computer helped...
I am an idiot sometimes :c
Also, I have the latest CM10 nightly.
Is that the problem? (Prob isn't because it will detect it while normal)
Guys, i just bought an used Nexus 4 and after flashing the cwm recovery and trying to boot in the recovery mode i get a few errors stating:
cant mount cache/recovery
cant open cache/recovery
I notice there are a few topics about this and the solution is to adb push or something, but the adb push command wont work in recovery for me, says device not found and i know my drivers are correct since i can fastboot and do stuff.
I actually got the device running perfectly flashing Chroma via sideload, but cwm wont work! I cant access anything from inside cwm... I also tried twrp and no luck.
I also tried a full original image flash, no luck
Can you please help me with this?
Thanks
luizffgarcia said:
Guys, i just bought an used Nexus 4 and after flashing the cwm recovery and trying to boot in the recovery mode i get a few errors stating:
cant mount cache/recovery
cant open cache/recovery
I notice there are a few topics about this and the solution is to adb push or something, but the adb push command wont work in recovery for me, says device not found and i know my drivers are correct since i can fastboot and do stuff.
I actually got the device running perfectly flashing Chroma via sideload, but cwm wont work! I cant access anything from inside cwm... I also tried twrp and no luck.
I also tried a full original image flash, no luck
Can you please help me with this?
Thanks
Click to expand...
Click to collapse
when you flashed the factory image it should have brought you back erasing and replacing everything. In fastboot did you flash the bootloader, radio, system partitions (.IMG), recovery partition, and so on.? If not try this steps guide http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312/page194 its pretty detailed but it helped me after I wiped everything off my phone trying to learn. If that's a bit too much then try searching for wugfresh nexus toolkit. Both will wipe everything from your nexus then replace it and should get everything going
Hello to everybody, so i was thinking my nakasi was really dead this time, the last thing i did was flashing a 5.1.1 rom next when i rebooted got stuck on lolipop boot loop so i restarted the tablet
manually to access the recovery, and to my awe, i couldn't no more access the recovery ! (latest twrp) tried again and again nothing, no recovery no bootloader, can't start the OS
always stuck on google logo with the options above, start, bootloader, recovery etc, today i realized i could access the bootloader and fastboot mode (ADB recognize my device when i type fastboot devices)
so i tried flashing stock image and stuff with no luck, tried many stock roms, tried wug's toolkit and the flash all.bat still no luck, i get all kind of error messages here is a screenshot, help is really appreciated if there is anything i can do to save it :
View attachment 3305126
the problem seems to be that i can't write the things i send to the tablet via ADB, tried the NVflash recovery today and got :
View attachment 3306049
Have you tried not imputing the full file address as you have the emulator already running from that location.
So recovery command would be.
Fastboot flash recovery "name of recovery Img file here"
Just make sure that the image file is in the platform-tools folder.
Probably not your issue but its going to save you some typing.
Good luck
gaosphappy said:
Have you tried not imputing the full file address as you have the emulator already running from that location.
So recovery command would be.
Fastboot flash recovery "name of recovery Img file here"
Just make sure that the image file is in the platform-tools folder.
Probably not your issue but its going to save you some typing.
Good luck
Click to expand...
Click to collapse
Thank you for the tip I'll certainly use it, but i don't think it is the culprit since as you can see in the screenshots
the files get sent successfully but cannot be written, my bootloader is unlocked by the way
Homurato said:
Thank you for the tip I'll certainly use it, but i don't think it is the culprit since as you can see in the screenshots
the files get sent successfully but cannot be written, my bootloader is unlocked by the way
Click to expand...
Click to collapse
Did you try the latest factory image? I noticed you are flashing a very old bootloader, possibly the first one? 4.23 is the current version.
Where is flatline_grouper.img coming from? I've never seen that.
adomol said:
Did you try the latest factory image? I noticed you are flashing a very old bootloader, possibly the first one? 4.23 is the current version.
Where is flatline_grouper.img coming from? I've never seen that.
Click to expand...
Click to collapse
Hello kind sir, of course at first i tried the 5.1.1 full factory image with the NRT toolkit and got the same writing errors next i tried many bootloaders
(one of them found it here as a 100% working bootloader) the Flatline is the recovery of the NVflash tool where you can access it to unbrick full bricked N7s
if you got blobs.bin of your N7 backed up (clearly not my case)
the flashing writing error i get it with everything i try to flash, recoverys bootloader system etc
when i send them with the flash all command they got sent to the tablet okay, but when writing i get the errors
i don't know but there is a small informations if that can help, before it broke my system was in EXT4 and all the rest in F2FS
It's entirely possible your memory has failed. I'm reading more and more people running into corrupted memory issues.
You can get a replacement motherboard cheap on eBay if nothing else works.
fwayfarer said:
It's entirely possible your memory has failed. I'm reading more and more people running into corrupted memory issues.
You can get a replacement motherboard cheap on eBay if nothing else works.
Click to expand...
Click to collapse
I'm still hoping for a software solution since my fastboot works fine, I'll let the motherboard solution my last i guess
Hello some news about the still staggering situations : when the tablet is off and i put the charger i get the battery refiling animation ! so that mean the bootloader isn't broken
and i still can access fastboot mode, even when i push a bootloader i get a signature match message, but the problem is still that the things i push can't be written as i'm still getting a :
FAILED <Remote: <FileWriteFailed>> changed usb cables, changed ports, the last time the tablet was working i had the system on EXT4 and the rest on F2FS, maybe if i can convert everything to EXT4 ?
Please help. I already tried everything that I've found to solve this issue. But still no luck.
So here's my problem:
First of all, my phone actually boots to droidboot. The bootloader is also locked and I'm sure because when I try to flash twrp recovery.img thru fastboot, it won't flash. Next thing is even if I unlock the bootloader using the fastboot flash method, still it's not working. The phone doesn't boot to Android but fastboot, droidboot and recovery works but the thing is I can't flash or modify anything. xFSTK won't work since droidboot is working. So, I'm pretty stuck to this situation right now. And also, /cache mount errors in either droidboot or recovery.
Thanks in advance.
---EDIT, FIXED IT ALREADY, MORE INFO BELOW---
Dear members,
A little background; The installation of the latest Oxygen os (zip on storage - > twrp flash) failed.
I thought it was a good idea to wipe everything and reboot to start fresh.
Upon reboot I was unable to enter TWRP, only fastboot was possible.
When I flash twrp (by neither clockworkx or the bluex) the flash is successful but I cant boot into the recovery, also not by directly using fastboot boot recovery.img. When booting into recovery I get a black screen with only a white led.
So I decided to give the stock recovery a try and that one does boot up however I cant flash anything. When I use adb sideload it loads the file fine but then it errors with no error message.
I am getting suspicious that my internal memory is now corrupt so I am willing to give this msmtool a try which I have never touched so I would really appreciate some guidance. Anyone with any ideas? Thanks a lot in advance.
Other things I have tried:
I tried to flash the stock boot.img from the oxygen os using fastboot but it doesnt seem to be the problem.
---FIXED:---
Thanks to the wonderful documentation found at : /oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
I was able to fix it. If you are in the same pickle head over to his thread and thank him.