Related
ok so here is the deal, been running mytouch4g for a while now rooted, cm7 etc last week phone started acting funny, required batt out reboots if camera app was on when unit went to sleep, now will not boot only boots to fastboot, can not flash anything.
Any ideas? at least an idea to remove cm signs so I can exchange unit.
thanks
zendick said:
ok so here is the deal, been running mytouch4g for a while now rooted, cm7 etc last week phone started acting funny, required batt out reboots if camera app was on when unit went to sleep, now will not boot only boots to fastboot, can not flash anything.
Any ideas? at least an idea to remove cm signs so I can exchange unit.
thanks
Click to expand...
Click to collapse
There should be an option on fastboot to go to bootloader and then from there recovery should be available, is that option available to you?
yes but recovery won't boot, sits at mt4g boot screen or sits at 3 skaters in center screen, depending on how I access it (ie go to fastboot then back again)
Power down your phone, hold volume down and the power button. That will take you into the hboot screen. You can then select to go into recovery from there.
thats what I have tried, it goes to three skaters center screen does nothing
I have tried flashing recovery from fastboot
tried hboot from fastboot
tried radio from fastboot
NOTHING flashes trust me I have been androiding for a while now never had I had a problem like this.
zendick said:
thats what I have tried, it goes to three skaters center screen does nothing
Click to expand...
Click to collapse
Is three skaters your boot animation or splash screen? Not sure what that is referring to.
the three skaters is the image at bottom of hboot screen, when i select recovery they go to center screen and nothing happens
zendick said:
the three skaters is the image at bottom of hboot screen, when i select recovery they go to center screen and nothing happens
Click to expand...
Click to collapse
Oh ok, i know what your talking about now. Your on the bootloader screen under fastboot. And when you select recovery option it does not boot into recovery?
correct and like i said I have tried to reflash everything from fastboot but no go
Just tried RUU it doesn't work it says rebooting to bootloader phone reboots to mytouch4g splash and ruu eventually gives usb error
got recovery to boot but get
e:can't mount /cache/recovery/command
etc
tried to mount, tried to format
no go
What do you mean tried ruu??
zendick said:
Just tried RUU it doesn't work it says rebooting to bootloader phone reboots to mytouch4g splash and ruu eventually gives usb error
Click to expand...
Click to collapse
Edit: nvm. Is doing RUU better option than loading PD15IMG.ZIP on sdcard and doing it that way?
Sent from my SGH-T959 using XDA App
tried a pd15 and it doesn't complete, drops a failed message
Sounds like you maybe victim of fail-pu. But if thats not the case and you don't care about your "/data" and just want working phone again then I suggest from fastboot you do "fastboot flash recovery recovery.img" which will replace the current recovery.img and flash it to mmcblk0p21. Once thats done do "fastboot erase system -w" and it will nuke everything so /system, /data, ect will all be erased. After that you can enter recovery by selecting it from hboot and then do factory wipe and flash another rom.
Keep in mind you will run in to errors in recovery after -w as its normal but depending on the fail-pu if you do get the failed partition update flag you can't make any changes as the errors will stick because you can't format the drives. Also the new recovery.img for CWMR can be found in dev section if not post here and ill send you.
I don't care at all about the data (I am well backed up) but I can't flash a recovery I have tried through fastboot, I agree the partition is F_D but I will try the erase system -w and see if that lets me do anything
thanks
uhg i think i may be foooked
C:\android-sdk\tools>fastboot flash recovery recovery2512.img
sending 'recovery' (4000 KB)...
OKAY [ 1.273s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 4.161s
C:\android-sdk\tools>fastboot erase system -w
erasing 'system'...
FAILED (remote: erasing error!)
finished. total time: 0.014s
Exactly what I got too, seems we have bricked our phones. Wish I had a way of making the phone unable to boot to recovery or at all.
zendick said:
uhg i think i may be foooked
C:\android-sdk\tools>fastboot flash recovery recovery2512.img
sending 'recovery' (4000 KB)...
OKAY [ 1.273s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 4.161s
C:\android-sdk\tools>fastboot erase system -w
erasing 'system'...
FAILED (remote: erasing error!)
finished. total time: 0.014s
Click to expand...
Click to collapse
Sent from my SGH-T959 using XDA App
I dont get how a phone can run for weeks since its last flash and have this happen, I made no changes updates etc just running as normal.
Is there a way to wipe evidence of cm of so I can get this phone repaired? To me this obviously a faulty emmc, I just can't see it being anything else.
or is it possible to boot recovery on sd like the nook?
any ideas on how to wipe cm bits atleast?
Hello guys, i've been trying to install a custom recovery on my Nexus 4 but it has been unsuccessful all the time.
The problem is just that I can't get to boot into the custom recovery, When i flash or temporarily boot a custom recovery with fast boot (fastboot flash recovery.IMG or fastboot boot recovery.IMG) it goes without any errors, but the problem comes when its time boot into the recovery, it just stays frozen at the Google screen and then i have to do a battery pull to get out of there.
I hope you can help me guys because i cant even root my phone without a custom recovery. Ive tried rooting using the Nexus roottoolkit but it doesnt work... Apparently my phone also cant boot a custom boot.img because it also stays frozen at the google screen. My phone is unlocked...
Thanks!:laugh:
Guillermo095 said:
Hello guys, i've been trying to install a custom recovery on my Nexus 4 but it has been unsuccessful all the time.
The problem is just that I can't get to boot into the custom recovery, When i flash or temporarily boot a custom recovery with fast boot (fastboot flash recovery.IMG or fastboot boot recovery.IMG) it goes without any errors, but the problem comes when its time boot into the recovery, it just stays frozen at the Google screen and then i have to do a battery pull to get out of there.
I hope you can help me guys because i cant even root my phone without a custom recovery. Ive tried rooting using the Nexus roottoolkit but it doesnt work... Apparently my phone also cant boot a custom boot.img because it also stays frozen at the google screen. My phone is unlocked...
Thanks!:laugh:
Click to expand...
Click to collapse
fastboot flash recovery recoveryname.img not fastboot flash recoveryname.img. you have to tell it which partition it goes into.
simms22 said:
fastboot flash recovery recoveryname.img not fastboot flash recoveryname.img. you have to tell it which partition it goes into.
Click to expand...
Click to collapse
OK. I just tried that and still nothing it hangs up on the Google screen... But that can't be the problem because booting it temporarily would have worked anyways...
fastboot oem unlock
Guillermo095 said:
OK. I just tried that and still nothing it hangs up on the Google screen... But that can't be the problem because booting it temporarily would have worked anyways...
Click to expand...
Click to collapse
try it 2 or 3 times in a row
fastboot oem unlock
Sent from my Nexus 4 using xda premium
androidtoy09 said:
fastboot oem unlock
Click to expand...
Click to collapse
this, if you havent done it yet.
simms22 said:
this, if you havent done it yet.
Click to expand...
Click to collapse
It says failed because i´m already unlocked, and also tried flashing multiple times but it still stays at the google screen...
Are you getting the boot loader screen? You should see the word start in green letters at the top.
If so then you may be flashing the wrong recovery.
If you have the right one try flashing the bootloader
Sent from my Nexus 4 using xda premium
kthejoker20 said:
Are you getting the boot loader screen? You should see the word start in green letters at the top.
If so then you may be flashing the wrong recovery.
If you have the right one try flashing the bootloader
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Yes, the bootloader works perfectly... I´m flashing the recovery through there... I don´t think I have the wrong recovery, I downloaded it from clockworkmod.com/rommanager and I have the latest Jelly Bean 4.2.2
Guillermo095 said:
Yes, the bootloader works perfectly... I´m flashing the recovery through there... I don´t think I have the wrong recovery, I downloaded it from clockworkmod.com/rommanager and I have the latest Jelly Bean 4.2.2
Click to expand...
Click to collapse
Could you try another custom recovery like TWRP. Might be an incomplete or corrupted download as well (Check md5sum before flashing).
I would download it directly from clockworkmod. Google it.
The make sure you put it in the same folder that your fast boot is in. Rename the file to recovery.img
Then at boot loader type fastboot flash recovery recovery.img
Sent from my Nexus 4 using xda premium
I tried both of your solutions but still nothing, I really don't understand why it doesn't allow custom recoveries :S
Guillermo095 said:
I tried both of your solutions but still nothing, I really don't understand why it doesn't allow custom recoveries :S
Click to expand...
Click to collapse
Make sure your SDK/ADB is up to date. Older versions have issues with flashing files to the Nexus 4 that can cause your phone to get stuck at boot. If your N4 isn't booting at all, you might want to reflash the entire stock software using the download from Google's Nexus build page, after you've updated your SDK/ADB suite, just to make sure your partition tables haven't gotten messed up.
you could try downloadong the stock rom from google then flashall file.
then try to install the custom recovery after it reset
Sent from my Nexus 4 using xda premium
Guillermo095 said:
I tried both of your solutions but still nothing, I really don't understand why it doesn't allow custom recoveries :S
Click to expand...
Click to collapse
hello,
I have exactly the same problem .... what finally made?
My device now is Rooted with superSU but with no custom recovery.
I return to stock recovery (after downloading the stock rom and flash only the recovery)
bbsnick said:
hello,
I have exactly the same problem .... what finally made?
My device now is Rooted with superSU but with no custom recovery.
I return to stock recovery (after downloading the stock rom and flash only the recovery)
Click to expand...
Click to collapse
I have same problem, when i install custom recovery it goes as follows(completes without error)
boot flash recovery recovery-clockwork-touch-6.0.3.1-mako.img
sending 'recovery' (7560 KB)...
OKAY [ 0.475s]
writing 'recovery'...
OKAY [ 0.402s]
finished. total time: 0.877s
but when I try to go into custom recovery, it shoes android bot icon with back open and exclamation mark.
Then when i ran
boot boot recovery-clockwork-touch-6.0.3.1-mako.img
downloading 'boot.img'...
OKAY [ 0.475s]
booting...
OKAY [ 0.021s]
finished. total time: 0.498s
It booted into custom recovery, but custom recovery was never installed. Any help?
1. Rename CWM to recovery.img (not recovery.img.img)
2. fastboot flash recovery recovery.img
3. fastboot reboot-bootloader
4. Done
EddyOS said:
1. Rename CWM to recovery.img (not recovery.img.img)
2. fastboot flash recovery recovery.img
3. fastboot reboot-bootloader
4. Done
Click to expand...
Click to collapse
It worked, thanks
I've unlocked the bootloader on my N4 with the following two commands:
adb reboot bootloader
fastboot oem unlock
Click to expand...
Click to collapse
Now I want to flash a custom recovery. After
adb reboot bootloader
Click to expand...
Click to collapse
I do see an opened bootloader, but when I execute
fastboot flash recovery openrecovery-twrp-2.5.0.0-mako.img
Click to expand...
Click to collapse
it gives me the following error message:
sending 'recovery' (4 KB)...
OKAY [ 0.004s]
writing 'recovery'...
FAILED (remote: image is not a boot image)
finished. total time: 0.006s
Click to expand...
Click to collapse
what am I missing?
When I boot the phone, I don't see the unlocked padlock beneath the Google logo. Does it mean that my unlocking didn't really work?
Thanks!
When you did fastboot OEM unlock did you confirm it by pressing yes on the phone? Then do fastboot reboot-bootloader
Also download the recovery.IMG again could have been a bad download
Sent from my Nexus 4
spaceman860 said:
When you did fastboot OEM unlock did you confirm it by pressing yes on the phone?
Click to expand...
Click to collapse
Yes I did that.
Then do fastboot reboot-bootloader
Click to expand...
Click to collapse
You mean right after "fastboot OEM unlock"? If so, no I didn't run that, and I simply rebooted the phone. Should I have gone through this step? The guide I was following does not mention this step. After I booted the phone, I ran 'fastboot reboot bootloader' before the recovery flash.
Also download the recovery.IMG again could have been a bad download
Click to expand...
Click to collapse
OK, I'll try another download later.
Thanks!
Are you using this guide
http://forum.xda-developers.com/showthread.php?t=2266654
Nexus 4 Guide-Unlock Bootloader, Root, Install Custom Recoveries & Custom ROMs/Kernel
Sent from my Nexus 4
spaceman860 said:
Are you using this guide
http://forum.xda-developers.com/showthread.php?t=2266654
Nexus 4 Guide-Unlock Bootloader, Root, Install Custom Recoveries & Custom ROMs/Kernel
Click to expand...
Click to collapse
Yes, that's the guide I followed!
Now I realized this might be the problem? Right after the boatloader was unlocked, maybe I should have continued to the recovery flash step? I didn't do that, and instead I simply rebooted the phone, and then started the recovery flash after I logged into the phone.
If this is the problem, how can I correct the misstep?
Thanks!
This isn't the problem.
Once you have unlocked the boot loader you should be able to flash the recovery at any point afterwards.
But not having the padlock would suggest that you are not unlocked.
Do fastboot reboot bootloader again.
Near the bottom it should tell you if your locked or unlocked
Sent from my Nexus 4 using xda app-developers app
Just go back to bootloader mode do
Fastboot OEM unlock
Select yes on phone then
Fastboot reboot-bootloader
It should say unlocked on the phone screen
Then flash the recovery.IMG again
Sent from my Nexus 4
Alex240188 said:
This isn't the problem.
Once you have unlocked the boot loader you should be able to flash the recovery at any point afterwards.
But not having the padlock would suggest that you are not unlocked.
Do fastboot reboot bootloader again.
Near the bottom it should tell you if your locked or unlocked
Click to expand...
Click to collapse
Well, I just booted into the bootloader mode now:
adb reboot bootloader
Click to expand...
Click to collapse
and I see the last line (same as the first time I ran the unlock command):
LOCK STATE - unlocked
Click to expand...
Click to collapse
So this means the bootloader is unlocked, right? On the other hand, when I boot the phone, I don't see the unlocked padlock beneath the Google logo. This is puzzling!
Just go back to bootloader mode do
Fastboot OEM unlock
Select yes on phone then
Fastboot reboot-bootloader
It should say unlocked on the phone screen
Then flash the recovery.IMG again
Click to expand...
Click to collapse
Again I just tried booting into the bootloader mode now again. When I unlocked again, it complained:
fastboot oem unlock
Click to expand...
Click to collapse
...
FAILED (remote: Already Unlocked)
finished. total time: 0.001s
After that, I did
adb reboot bootloader
Click to expand...
Click to collapse
error: device not found
And then
fastboot flash recovery openrecovery-twrp-2.5.0.0-mako.img
Click to expand...
Click to collapse
sending 'recovery' (4 KB)...
OKAY [ 0.002s]
writing 'recovery'...
FAILED (remote: image is not a boot image)
finished. total time: 0.004s
I'm lost...
Did you download it from here
http://goo.im/devs/OpenRecovery/mako/openrecovery-twrp-2.5.0.0-mako.img
Also try a different USP port on your computer
Sent from my Nexus 4
spaceman860 said:
Did you download it from here
http://goo.im/devs/OpenRecovery/mako/openrecovery-twrp-2.5.0.0-mako.img
Also try a different USP port on your computer
Sent from my Nexus 4
Click to expand...
Click to collapse
No, from here:
http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.5.0.0-mako.img
Any difference between the two?
Also when I boot up the phone, I don't see the opened bootpad. Does it mean it's not really unlocked?
Problem fixe!
spaceman860 said:
Also download the recovery.IMG again could have been a bad download
Click to expand...
Click to collapse
It was indeed a bad download. Once I downloaded another copy, everything went smoothly.
Thanks everybody for the kind help and suggestions!
mj56gt said:
Problem fixe!
It was indeed a bad download. Once I downloaded another copy, everything went smoothly.
Thanks everybody for the kind help and suggestions!
Click to expand...
Click to collapse
i am having a same problem,but on different device,huawei y336-u02,in my country it called "Y3 Batik Edition" (Indonesian Thing),But In This Case I Want To Flash boot.img that has been patched using magisk manager,help me please
I'm not familiar with flashing rom, just root the N7 for OTG and some Apps.
But it's unable to update by system update from 421 to 422 recently.
It shows a lying Android with exclamation mark and "no command".
So I try to flash stock rom with Asus root toolkit,
but it halted at bootloader very soon, when I press the power it shows "booting failed"
It is not success when I try to flash 421 or 422
I also try to flash stock recovery, it shows lying Android.
But it's ok to flash CWM or Teamwin, and show that there is problem on mounting sd card
Please advise what I can do
Thanks in advance.
Are you able to boot into the recovery menu or boot loader?
---------- Post added at 06:28 PM ---------- Previous post was at 06:08 PM ----------
If you can get into recovery menu then wipe data/system and flash a new ROM of your choice. If you can't get into recovery but can get into the bootloader then flash CWM or TWRP recovery using fastboot, then flash a new ROM of your choice in the new recovery menu.
I see no reason why this can't be fixed unless you can't get into the bootloader menu... At that point its beyond my knowledge.
Yes, I can flash CWM and Teamwin but not stock
Bootloader ok but when press Start it shows booting failed
Can enter recovery, but both show cant mount cache and sd card
Organized_Chaos said:
Are you able to boot into the recovery menu or boot loader?
---------- Post added at 06:28 PM ---------- Previous post was at 06:08 PM ----------
If you can get into recovery menu then wipe data/system and flash a new ROM of your choice. If you can't get into recovery but can get into the bootloader then flash CWM or TWRP recovery using fastboot, then flash a new ROM of your choice in the new recovery menu.
I see no reason why this can't be fixed unless you can't get into the bootloader menu... At that point its beyond my knowledge.
Click to expand...
Click to collapse
What happens when you do it from command line using adb/fastboot? That should probably give you more detailed info on why it failed.
Jack425 said:
Yes, I can flash CWM and Teamwin but not stock
Bootloader ok but when press Start it shows booting failed
Can enter recovery, but both show cant mount cache and sd card
Click to expand...
Click to collapse
Forget about the root toolkit and use fastboot in command line. There are tutorials on this.
Download newest stock 4.2.2 from google.
Open command.
Put n7 in bootloader
Type-
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot reboot-bootloader
sleep 10
fastboot -w update image-nakasi-jrn84d.zip
Replace "bootloader-grouper-3.34.img" and "image-nakasi-jrn84d.zip" with the new ones you downloaded.
Once done, you can unlock the bootloader again using "fastboot oem unlock" , and the re-root and install custom recovery, then flash custom roms all you want.
Sent from my SGH-I727 using xda premium
Organized_Chaos said:
What happens when you do it from command line using adb/fastboot? That should probably give you more detailed info on why it failed.
Click to expand...
Click to collapse
for CWM, I can see the following
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
for Teamwin
E:Unable to mount '/system'
E:Unable to mount '/cache'
E:Unable to mount '/cache'
E:TWFunc::Copy_Log, --Can't open destination log file: '/cache/recovery/log'
E:Unable to mount '/cache'
All wipe or Fix permission on recovery are tried, are there any information I provided are not clear, sorry that I mainly use the toolkit and not so familiar with command line, thanks
rebel1699 said:
Forget about the root toolkit and use fastboot in command line. There are tutorials on this.
Download newest stock 4.2.2 from google.
Open command.
Put n7 in bootloader
Type-
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot reboot-bootloader
sleep 10
fastboot -w update image-nakasi-jrn84d.zip
Replace "bootloader-grouper-3.34.img" and "image-nakasi-jrn84d.zip" with the new ones you downloaded.
Once done, you can unlock the bootloader again using "fastboot oem unlock" , and the re-root and install custom recovery, then flash custom roms all you want.
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
Hi, I followed the steps, but after reboot-bootloader, the N7 just stay at bootloader"START", even I proceed to update image
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.18
Baseband Version.....: 1231------------
Serial Number........: 01--------------
--------------------------------------------
checking product...
OKAY [ 0.047s]
checking version-bootloader...
OKAY [ -0.000s]
checking version-baseband...
FAILED
Device version-baseband is '1231_0.10.0_1021'.
Update requires '1231_0.17.0_1205'.
finished. total time: 0.281s
After all commands are executed, the screen is staying at "START", it shows "booting failed" when I press power, and the recovery need to be flashed again
Jack425 said:
Hi, I followed the steps, but after reboot-bootloader, the N7 just stay at bootloader"START", even I proceed to update image
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.18
Baseband Version.....: 1231------------
Serial Number........: 01--------------
--------------------------------------------
checking product...
OKAY [ 0.047s]
checking version-bootloader...
OKAY [ -0.000s]
checking version-baseband...
FAILED
Device version-baseband is '1231_0.10.0_1021'.
Update requires '1231_0.17.0_1205'.
finished. total time: 0.281s
After all commands are executed, the screen is staying at "START", it shows "booting failed" when I press power, and the recovery need to be flashed again
Click to expand...
Click to collapse
So after typing "fastboot reboot bootloader" it doesnt reboot back to the bootloader? It just stays there?
Sent from my SGH-I727 using xda premium
rebel1699 said:
So after typing "fastboot reboot bootloader" it doesnt reboot back to the bootloader? It just stays there?
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
it rebooted, dark for 1-2 seconds, google screen flash less than 1sec and return the bootloader-Start again
Jack425 said:
it rebooted, dark for 1-2 seconds, google screen flash less than 1sec and return the bootloader-Start again
Click to expand...
Click to collapse
Thats exactly what it is suppose to do. The command "fastboot reboot bootloader" means reboot back into the bootloader so the bootloader flash can set in and you can issue the rest of the commands. After it reboots to bootloader, it is time to flash the os. "Fastboot flash update -w "version you downloaded here.zip
Sent from my SGH-I727 using xda premium
rebel1699 said:
Thats exactly what it is suppose to do. The command "fastboot reboot bootloader" means reboot back into the bootloader so the bootloader flash can set in and you can issue the rest of the commands. After it reboots to bootloader, it is time to flash the os. "Fastboot flash update -w "version you downloaded here.zip
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
checking product...
OKAY [ 0.031s]
checking version-bootloader..
OKAY [ 0.016s]
checking version-baseband...
FAILED
Device version-baseband is '1
Update requires '1231_0.17.0_
finished. total time: 0.187s
But it is still at Bootloader-Start when above commands finished, I press the power and got "booted Failed"
after restart bootloader, both Start and Recover Mode got "booted Failed" on left corner
Jack425 said:
checking product...
OKAY [ 0.031s]
checking version-bootloader..
OKAY [ 0.016s]
checking version-baseband...
FAILED
Device version-baseband is '1
Update requires '1231_0.17.0_
finished. total time: 0.187s
But it is still at Bootloader-Start when above commands finished, I press the power and got "booted Failed"
after restart bootloader, both Start and Recover Mode got "booted Failed" on left corner
Click to expand...
Click to collapse
It looks like you are trying to flash a custom rom through fastboot. You cant do that. You have to download the official stock image from google.
Sent from my SGH-I727 using xda premium
rebel1699 said:
It looks like you are trying to flash a custom rom through fastboot. You cant do that. You have to download the official stock image from google.
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
I was downloaded from https://dl.google.com/dl/android/aosp/nakasig-jdq39-factory-0798439d.tgz
and extract >nakasig-jdq39-factory-0798439d.tar> nakasig-jdq39
to get bootloader-tilapia-4.18.img and image-nakasig-jdq39.zip
I just tried again to download and flash again, the bootloader show "signature match." after flashed the bootloader.
Jack425 said:
I was downloaded from https://dl.google.com/dl/android/aosp/nakasig-jdq39-factory-0798439d.tgz
and extract >nakasig-jdq39-factory-0798439d.tar> nakasig-jdq39
to get bootloader-tilapia-4.18.img and image-nakasig-jdq39.zip
I just tried again to download and flash again, the bootloader show "signature match." after flashed the bootloader.
Click to expand...
Click to collapse
The image you downloaded is for the Nexus 7 3G. Do you have the wifi or 3G model?
Sent from my Nexus 7 using xda premium
rebel1699 said:
The image you downloaded is for the Nexus 7 3G. Do you have the wifi or 3G model?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Yes, my one is N7 3G
Jack425 said:
Yes, my one is N7 3G
Click to expand...
Click to collapse
Ok, then if the bootloader is flashing correctly, but the image-nakasig-jdq39.zip is not, then you have yourself a brick, more than likely.
Sent from my Nexus 7 using xda premium
LOL, i just got it yesterday. i made a mistake when wipe all my data and os :laugh: so it cannot start but luckily i still start bootloader.
u can use a 2gb usb to mount image-nakasig-jdq39.zip (i try with a 4gb usb but it cannot mount). Then now it's ok. Hope this usefut 4 u
ceballos124 said:
LOL, i just got it yesterday. i made a mistake when wipe all my data and os :laugh: so it cannot start but luckily i still start bootloader.
u can use a 2gb usb to mount image-nakasig-jdq39.zip (i try with a 4gb usb but it cannot mount). Then now it's ok. Hope this usefut 4 u
Click to expand...
Click to collapse
hi, which recovery did u use ?
Thanks to everyone advised to me,
as I find that the process of fastboot -w update image-nakasig-jdq39.zip is very short,
I try to unzip and flash .img one by one,
Finally, I can boot into Android, just found that the recovery is still "Lying Android"
My main rooted v20 phone got bumped and now is stuck in a bootloop. I can enter fastboot (some commands working) but can't access TWRP recovery using either VOL + UP and USB cable or VOL DOWN + POWER. I believe the phone is on 10j or 10k if I remember correctly. Bootloader and carrier are unlocked.
Is there a way to just reflash TWRP safely and attempt data recovery and ROM installation without factory reset?
My goal is to attempt recovery first. If that is not an option, I would like to flash to 10p so I can start the rooting process using Lafsploit.
DirtyBreakz said:
My main rooted v20 phone got bumped and now is stuck in a bootloop. I can enter fastboot (some commands working) but can't access TWRP recovery using either VOL + UP and USB cable or VOL DOWN + POWER. I believe the phone is on 10j or 10k if I remember correctly. Bootloader and carrier are unlocked.
Is there a way to just reflash TWRP safely and attempt data recovery and ROM installation without factory reset?
My goal is to attempt recovery first. If that is not an option, I would like to flash to 10p so I can start the rooting process using Lafsploit.
Click to expand...
Click to collapse
Sure, to flash twrp in fastboot mode you do this.
Download latest twrp
With the phone off hold vol down plug USB into phone and computer.
type on your computer:
fastboot flash recovery twrp-3.6.2_9-0-h918.img
fastbboot reboot
take battery out
put back in
go into twrp by doing a factory reset. How to factory reset the Lgv20
U
Darnrain1 said:
Sure, to flash twrp in fastboot mode you do this.
Download latest twrp
With the phone off hold vol down plug USB into phone and computer.
type on your computer:
fastboot flash recovery twrp-3.6.2_9-0-h918.img
fastbboot reboot
take battery out
put back in
go into twrp by doing a factory reset. How to factory reset the Lgv20
Click to expand...
Click to collapse
Unfortunately no joy. I tried fastboot boot and flash commands and even tried renaming the img file. I tried with 3 different versions of twrp. This was the result:
PS C:\Users\User\NexusTools> fastboot boot twrp-3.6.2_9-0-h918.img
Sending 'boot.img' (24948 KB) OKAY [ 0.771s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
Click to expand...
Click to collapse
PS C:\Users\User\NexusTools> fastboot flash recovery twrp.img
Sending 'recovery' (23512 KB) OKAY [ 0.854s]
Writing 'recovery' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Click to expand...
Click to collapse
I've searched the forums and internet for hours and not coming up with anything. Any other ideas?
Just a note when trying to cold boot to twrp using 'UP VOLUME + CONNECT USB' that the screen flashes download mode for a split second and then reboots.
DirtyBreakz said:
U
Unfortunately no joy. I tried fastboot boot and flash commands and even tried renaming the img file. I tried with 3 different versions of twrp. This was the result:
I've searched the forums and internet for hours and not coming up with anything. Any other ideas?
Just a note when trying to cold boot to twrp using 'UP VOLUME + CONNECT USB' that the screen flashes download mode for a split second and then reboots.
Click to expand...
Click to collapse
That's so odd I have never seen this issue before.
You can try flashing the twrp image to the boot partition.
fastboot flash boot twrp.img
fastboot reboot
Should boot rite into twrp then because the twrp image is on the boot partition. Sounds to be like there may be a hardware problem with this phone.
Darnrain1 said:
That's so odd I have never seen this issue before.
You can try flashing the twrp image to the boot partition.
fastboot flash boot twrp.img
fastboot reboot
Should boot rite into twrp then because the twrp image is on the boot partition. Sounds to be like there may be a hardware problem with this phone.
Click to expand...
Click to collapse
Well unfortunately the flash boot command failed also. I'm guessing because it shows the boot partition size is 0. Any possible way around this?
I'm hoping not but I think you might be right about a possible hardware issue...
PS C:\Users\User\NexusTools> fastboot flash boot twrp.img
Warning: skip copying boot image avb footer (boot partition size: 0, boot image size: 24076288).
Sending 'boot' (23512 KB) OKAY [ 0.817s]
Writing 'boot' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Click to expand...
Click to collapse
DirtyBreakz said:
Well unfortunately the flash boot command failed also. I'm guessing because it shows the boot partition size is 0. Any possible way around this?
Click to expand...
Click to collapse
I think it's a hardware issue with the ram. I cant think of anything else.
Do a search online for the error message.
Writing 'boot' FAILED (remote: 'unknown command')