Related
Hi everyone, I'm new here and I have a GNex on my hands.
While I received it to fix; I could not get it past a bootloop from the nexus 4.0.4 Boot.
Problem is I cannot seem to get past the boot animation screen nor upgrade it.
Tried flashing another bootloader via fastboot, and the bootloader does not change, stays in same version.
HW Version : 9
Bootloader version : PRIMEKK15
Baseband version : I9250XXKK6
I proceed doing a fastboot erase bootloader and trying another bootloader, rebooting into another bootloader but no luck
Tried also ODIN flash but no luck; stays into the same
Booting into recovery mode goes into stock recovery and tries to flash a file from /cache
By trying to flash CWM via fastboot flash recovery <cwm image> flashes image but no luck on booting into CWM.
Anbody can lend a hand please?
Thanks!
jhonnyx said:
Hi everyone, I'm new here and I have a GNex on my hands.
While I received it to fix; I could not get it past a bootloop from the nexus 4.0.4 Boot.
Problem is I cannot seem to get past the boot animation screen nor upgrade it.
Tried flashing another bootloader via fastboot, and the bootloader does not change, stays in same version.
HW Version : 9
Bootloader version : PRIMEKK15
Baseband version : I9250XXKK6
I proceed doing a fastboot erase bootloader and trying another bootloader, rebooting into another bootloader but no luck
Tried also ODIN flash but no luck; stays into the same
Booting into recovery mode goes into stock recovery and tries to flash a file from /cache
By trying to flash CWM via fastboot flash recovery <cwm image> flashes image but no luck on booting into CWM.
Anbody can lend a hand please?
Thanks!
Click to expand...
Click to collapse
You can flash a custom recovery like cwm or twrp. Then you can acces the custom recovery and adb push your ROM and gapps. Then you do the wipes and flash the ROM and gapps. If you dont understand anything you just have to tell me
Sent from my Galaxy Nexus using XDA Premium HD app
Thanks mrgnex. I've tried flashing TWRP, but the only thing it does is boot into stock recovery and tries to flash a file from /cache/, which file is: 5a81769b6d01.signed-yakju-IMM76I-from-ICL53F.5a81769b.zip; pretty weird. Issue is the same as this thread: http://forum.xda-developers.com/showthread.php?t=1909331&page=4
use: fastboot boot recovery.img
and "recovery.img" which recovery do you suggest? twrp or a CWM in particular?
doesnt matter. whichever.
jhonnyx said:
and "recovery.img" which recovery do you suggest? twrp or a CWM in particular?
Click to expand...
Click to collapse
I suggest the latest TWRP.
http://www.teamw.in/project/twrp2
Edit: Have you read this?
TheMysteriousOne said:
I suggest the latest TWRP.
http://www.teamw.in/project/twrp2
Edit: Have you read this?
Click to expand...
Click to collapse
While now I'm trying to install latest TWRP (already did and no luck) I'm downloading the pack from the "Have you read this?".
The things that I'm seeing right now that seem to be wrong are:
1 - everytime I reboot the phone, the "fastboot oem unlock" seems to be gone and phone re-locks again (weird!)
2 - every change I make to the filesystem, seems to be non-persistent I/E: push something via adb push and on reboot it's gone! :/
Any help would be greatly appreciated.
jhonnyx said:
While now I'm trying to install latest TWRP (already did and no luck) I'm downloading the pack from the "Have you read this?".
The things that I'm seeing right now that seem to be wrong are:
1 - everytime I reboot the phone, the "fastboot oem unlock" seems to be gone and phone re-locks again (weird!)
2 - every change I make to the filesystem, seems to be non-persistent I/E: push something via adb push and on reboot it's gone! :/
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Can you elaborate on why exactly you were not able to install TWRP?
TheMysteriousOne said:
Can you elaborate on why exactly you were not able to install TWRP?
Click to expand...
Click to collapse
Surely:
1 - Unlock via fastboot oem unlock
2 - fastboot erase recovery (exits with ok)
3 - fastboot flash recovery twrp_versiondoesnotmatter.img (exits with ok)
4 - reboot w/power+vlup+voldown and select reboot recovery
5 - stock recovery appears
an alternate method that i've tried:
1 - Unlock via fastboot oem unlock
2 - fastboot boot twrp_versiondoesnotmatter.img (exits with ok)
3 - TWRP boots and flashes a zipfile from /cache/ then reboots automatically
That's what happens. A mistery, huh?
Also I've tried OMAP Flash, and; the same issue happens over and over again
Have you tried doing a factory reset using the stock recovery?
TheMysteriousOne said:
Have you tried doing a factory reset using the stock recovery?
Click to expand...
Click to collapse
AFAIK, Yes
What happens once I start the stock recovery; as I've already stated; starts flashing a zip file located into /cache/ (5a81769b6d01.signed-yakju-IMM76I-from-ICL53F.5a81769b.zip); then bleh, starts the bootloop again.
I've tried the power+volup then selected wipe cache and wipe system and it's the same.
Did you try flash google's stock images (all of them) ?
Also try flashing TWRP in the boot (kennel) partition by :-
Code:
fastboot flash boot <path to twrp>.img
This will force the phone into Recovery (But you will have recovery bootloop , can be solved by flashing a kernel) .
when you boot into recovery install a Kernel and ROM . also you will lose the recovery after that .
You can flash the TWRP from the TWRP itself (to put it in the right partition) by (in the build in terminal) :-
Code:
dd if=/<path to twrp in SD>.img of=/dev/block/mmcblk0p8
Good Luck .
Sent from my Galaxy Nexus using xda app-developers app
$Parker said:
Did you try flash google's stock images (all of them) ?
Also try flashing TWRP in the boot (kennel) partition by :-
Code:
fastboot flash boot <path to twrp>.img
This will force the phone into Recovery (But you will have recovery bootloop , can be solved by flashing a kernel) .
when you boot into recovery install a Kernel and ROM . also you will lose the recovery after that .
You can flash the TWRP from the TWRP itself (to put it in the right partition) by (in the build in terminal) :-
Code:
dd if=/<path to twrp in SD>.img of=/dev/block/mmcblk0p8
Good Luck .
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
fastboot flash boot <path to twrp>.img does not boot the recovery . I mean; still boots the normal Kernel.
Actually I'm trying what TheMysteriousOne told me by downloading the stock Gnex zip (250Mb) to flash via Odin.
Ohh, bad luck strikes again:
<ID:0/011> system.img
<ID:0/011> Complete(Write) operation failed.
cannot write system.img :/
Any ideas?
Unlock your bootloader with omapflash. Although even if it does unlock, Your emmc/board probably has died.
a manta wrote this.
beekay201 said:
Unlock your bootloader with omapflash. Although even if it does unlock, Your emmc/board probably has died.
a manta wrote this.
Click to expand...
Click to collapse
can you please me guide how to do the omapflash?
I've downloaded a file called OMAPFlash_tuna.zip.
- Set battery of the device aside
- Plug device into USB, let it detect the device and flash the SBF I think.
That'd be all?
beekay201 said:
Unlock your bootloader with omapflash. Although even if it does unlock, Your emmc/board probably has died.
a manta wrote this.
Click to expand...
Click to collapse
Pardon me, if EMMC/Board is dead; why does it boot or get into bootloop? There is something that reflashes itself; it even overrides odin or heimdall...
Have you tried going back to completely stock using the method outlined here? http://forum.xda-developers.com/showthread.php?t=1626895
jhonnyx said:
can you please me guide how to do the omapflash?
I've downloaded a file called OMAPFlash_tuna.zip.
- Set battery of the device aside
- Plug device into USB, let it detect the device and flash the SBF I think.
That'd be all?
Click to expand...
Click to collapse
Read this thread
http://forum.xda-developers.com/showthread.php?t=2016628
a manta wrote this.
Hi everyone. I bought this Find 7 today in hopes that I could get it running. The previous owner apparently went to flash cm11 and he soft bricked it. The phone will power on to the start screen the the screen stays black and goes on and off. I can get to fastboot but not recovery. I have read in the oppo forums that I need to push the stock recovery too it but am unfamiliar with fastboot.. Any input would be greatly appreciated. Thank you.
I got it to boot up following this thread http://forum.xda-developers.com/find-7/help/bricked-7-t2897376. Then I went to wipe it and I'm back where I started. The Msm Downloader is japanese so I don't understand what half of it means. Must have been a fluke it booted up.
I got it to boot up again. I'm not sure what I should do with it next. There is no recovery installed.
If you can get to fastboot, download a recovery, navigate to that recovery, use
fastboot flash recovery x.img
Where x is the name of the file. Hold down power and volume down until phone vibrates, and you should be in recovery
farenteria said:
If you can get to fastboot, download a recovery, navigate to that recovery, use
fastboot flash recovery x.img
Where x is the name of the file. Hold down power and volume down until phone vibrates, and you should be in recovery
Click to expand...
Click to collapse
Thank you for the response. I have been trying to do that. I have the recovery.img downloaded but I can't seem to get it to my phone. I'm not all that familiar with fastboot and adb.
Ethanp said:
Thank you for the response. I have been trying to do that. I have the recovery.img downloaded but I can't seem to get it to my phone. I'm not all that familiar with fastboot and adb.
Click to expand...
Click to collapse
Do you have fastboot and adb installed on your computer?
Yes I do
Ethanp said:
Thank you for the response. I have been trying to do that. I have the recovery.img downloaded but I can't seem to get it to my phone. I'm not all that familiar with fastboot and adb.
Click to expand...
Click to collapse
Which recovery are you trying to install??? OPPO stock recovery or other custom recoveries like TWRP??
By the way, as long as you can get into fastboot, everything is fixable, just a matter of how long it takes
Doomboss said:
Which recovery are you trying to install??? OPPO stock recovery or other custom recoveries like TWRP??
Click to expand...
Click to collapse
I was trying to install the Oppo stock recovery.img
Ethanp said:
I was trying to install the Oppo stock recovery.img
Click to expand...
Click to collapse
Ok, can you try to download the latest TWRP and see if you can install it with fastboot??
Doomboss said:
Ok, can you try to download the latest TWRP and see if you can install it with fastboot??
Click to expand...
Click to collapse
I just tried it and it says it cannot load
Ethanp said:
I just tried it and it says it cannot load
Click to expand...
Click to collapse
Hmm it looks like you put the .img file in the wrong path. Can you show me the command you entered and the name of the TWRP recovery image you downloaded?
Doomboss said:
Hmm it looks like you put the .img file in the wrong path. Can you show me the command you entered and the name of the TWRP recovery image you downloaded?
Click to expand...
Click to collapse
I'm not sure where the .img file should go. Do you have teamviewer?
Ethanp said:
I'm not sure where the .img file should go. Do you have teamviewer?
Click to expand...
Click to collapse
Yes I do. But I don't have time until 1 and half hour later
You can place the .img file anywhere you want, but you just have to specify the path and name of the recovery image on the fastboot flash command. For example: fastboot flash recovery C:\openrecovery-twrp-2.8.0.1-find7.img (this is if you put the recovery image in the root directory of C drive)
Doomboss said:
Yes I do. But I don't have time until 1 and half hour later
You can place the .img file anywhere you want, but you just have to specify the path and name of the recovery image on the fastboot flash command. For example: fastboot flash recovery C:\openrecovery-twrp-2.8.0.1-find7.img (this is if you put the recovery image in the root directory of C drive)
Click to expand...
Click to collapse
Ok I just got this message. Failed <remote: Device not unlocked cannot flash or erase. The phone is plugged in and in fastboot?
Ethanp said:
Ok I just got this message. Failed <remote: Device not unlocked cannot flash or erase. The phone is plugged in and in fastboot?
Click to expand...
Click to collapse
Try: fastboot oem unlock
I don't know if this will works directly since you probably don't have the OPPO driver and i'm not sure if you need it. By the way this method will wipe everything on the phone but i assume you don't have anything on the phone yet anyway :silly:
Doomboss said:
Try: fastboot oem unlock
I don't know if this will works directly since you probably don't have the OPPO driver and i'm not sure if you need it. By the way this method will wipe everything on the phone but i assume you don't have anything on the phone yet anyway :silly:
Click to expand...
Click to collapse
Ok fastboot oem unlock worked. The phone wiped and booted.
Ethanp said:
Ok fastboot oem unlock worked. The phone wiped and booted.
Click to expand...
Click to collapse
Did you also install the TWRP recovery? (By the way, you don't need the stock OPPO recovery since the newest TWRP can also flash ColorOS)
Doomboss said:
Did you also install the TWRP recovery? (By the way, you don't need the stock OPPO recovery since the newest TWRP can also flash ColorOS)
Click to expand...
Click to collapse
Yes I just successfully flashed twrp. Thank you very much for your help!
Ethanp said:
Yes I just successfully flashed twrp. Thank you very much for your help!
Click to expand...
Click to collapse
You're welcome Have fun with your Find 7!
Hi
Problem is that I can't enter recovery. I am able to enter fastboot menu, but when I'm choosing recovery mode, phone like restarts and goes again to fastboot menu...no recovery mode or dead bot with error comes. Below is blue writing "continue the fastboot process".
This happened after I tried to install twrp through twrp manager...it was installing twrp and said that install succesful.
Also tried fastboot command "fastboot clear cache", but nothing.
So, you didn't unlock the bootloader and removed your recovery...
1st thing, go to bootloader mode, download the recovery for your version of Android, eg 2.20.40.168, and flash through fastboot on the PC.
Put phone in fastboot (bootloader mode) - I'm assuming of course you have the latest Intel drivers and the flashing tools - and through the CMD interface (agasin flashing tools) type "fastboot devices". If you did it right then you'll see you serial number...
Now, in the same folder as the fastboot tools, have the recovery.img ready and type "fastboot flash recovery recovery.img".
You should now have recovery again...
2. If you haven't done so, lookup how to unlock bootloader before trying this again and do it. Make sure everything goes as it says, particularly important the splashscreen that says ASUS turns white, and you should be ok to flash TWRP though I use PC as I find everything seems to work.
Yes, it was my mistake, i didn't unlock bootloader and tried to flash twrp.
Now i can Go into fastboot and phone connects to pc easily.
But so far i didn't found recovery image for 2.20.40.174 fw.
But can you confirm that it's possible now to use one click bootloader unlock and then flash twrp? Without flashing stock recovery.
Jaaguar86 said:
Yes, it was my mistake, i didn't unlock bootloader and tried to flash twrp.
Now i can Go into fastboot and phone connects to pc easily.
But so far i didn't found recovery image for 2.20.40.174 fw.
But can you confirm that it's possible now to use one click bootloader unlock and then flash twrp? Without flashing stock recovery.
Click to expand...
Click to collapse
You can use This Apk to unlock bootloader.
Once unlocked it will reboot and show white splashscree,then you are ready to use twrp.
Try it
If you go to the pre-rooted rom thread you can download ALL the img files - rom, recovery,boot and droidboot.img. I'm pretty sure 174 was there in the Mega link at the top of the 1st post...
Just download the recovery.img as that's what you need...
Ok, thanks to all. Now bootloader is unlocked, twrp installed and installed rom blisspop. Great phone when there is no bloatware.
Sent from my ASUS_Z00A using XDA Premium 4 mobile app
Cool, glad you got your toy working again...
Same issue as sir Jaguar
Already installed .img trough adb says succesfully installed
When i go to recovery mode no deadbot no white splash screen load.
Tried the asus unlocking tool provided by the asus and the same link provided by sir Ultima still no good results.
Im already at 174 fw
Tried the twrp apk
Tried flashify
Tried diffrent kind of .img
Tried to re install the image using ADB
Still no good results
I think its the bootloader that has the problem.
Guys plz help tnx
thank you for your hard work!! love it
you can try to reflash the corresponding version of stock recovery.img
ultramag69 said:
If you go to the pre-rooted rom thread you can download ALL the img files - rom, recovery,boot and droidboot.img. I'm pretty sure 174 was there in the Mega link at the top of the 1st post...
Just download the recovery.img as that's what you need...
Click to expand...
Click to collapse
i can not find the link u r talking about .. please can u repost it i srsly need the recovery.img file
thanks in advance
amanbansal009 said:
i can not find the link u r talking about .. please can u repost it i srsly need the recovery.img file
thanks in advance
Click to expand...
Click to collapse
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Hi there, I have a similar problem i think. I have unlocked bootloader.
My problem is PC won't regonize my device. I installed the driver for intel asus adb but it would says "error: device not found" for fastboot cmd.
so now i m stuck in fastboot and can't do anything ...
Hi, Also have my phone on the same conditions but If I try to flash anything I got permission Denied.
Please help me
Ok let me start out by saying 99.99 percent of the time I can recover from a soft brick situation as I am very familiar with both ADB and Fastboot commands. However I cannot connect via ADB (ADB devices displays nothing) where as Fastboot devices does. I have flashed both twrp and stock recoveries with the same results. It cannot boot into recovery mode only Fastboot mode.
Suggestions are welcome thanks for any help anyone can provide.
Sent from my SM-G935T using Tapatalk
bkeaver said:
Ok let me start out by saying 99.99 percent of the time I can recover from a soft brick situation as I am very familiar with both ADB and Fastboot commands. However I cannot connect via ADB (ADB devices displays nothing) where as Fastboot devices does. I have flashed both twrp and stock recoveries with the same results. It cannot boot into recovery mode only Fastboot mode.
Suggestions are welcome thanks for any help anyone can provide.
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
If you are using Win10 PC or Laptop, the issue is with the drivers installed.
Search for Win10 issues in OP3 forum and you will get the answer. A simple solution is to use Win7 if you can.
Nope I pulled my windows7 pc out just because I know that win10 can be finicky
Sent from my SM-G935T using Tapatalk
bkeaver said:
Ok let me start out by saying 99.99 percent of the time I can recover from a soft brick situation as I am very familiar with both ADB and Fastboot commands. However I cannot connect via ADB (ADB devices displays nothing) where as Fastboot devices does. I have flashed both twrp and stock recoveries with the same results. It cannot boot into recovery mode only Fastboot mode.
Suggestions are welcome thanks for any help anyone can provide.
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/devdb/project/dl/?id=21065
Flash the above mentioned recovery by blusparks through fastboot since your fastboot is not an issue .....
It should make your recovery usable. Once done flash any of the oos builds, and before booting flash this same recovery trough twrp and supersu then restart.
You may have done this before, but humor me and do exactly as i asked you to...... Won't hurt.....
ajaysoranam said:
http://forum.xda-developers.com/devdb/project/dl/?id=21065
Flash the above mentioned recovery by blusparks through fastboot since your fastboot is not an issue .....
It should make your recovery usable. Once done flash any of the oos builds, and before booting flash this same recovery trough twrp and supersu then restart.
You may have done this before, but humor me and do exactly as i asked you to...... Won't hurt.....
Click to expand...
Click to collapse
Ok as soon as I get back home I'll give it a shot. I'm not above trying anything at this point.
Sent from my SM-G935T using Tapatalk
ajaysoranam said:
http://forum.xda-developers.com/devdb/project/dl/?id=21065
Flash the above mentioned recovery by blusparks through fastboot since your fastboot is not an issue .....
It should make your recovery usable. Once done flash any of the oos builds, and before booting flash this same recovery trough twrp and supersu then restart.
You may have done this before, but humor me and do exactly as i asked you to...... Won't hurt.....
Click to expand...
Click to collapse
ok I am now atleast in recovery but now its asking for a darn password to decrypt and its not the password it was.
ajaysoranam said:
http://forum.xda-developers.com/devdb/project/dl/?id=21065
Flash the above mentioned recovery by blusparks through fastboot since your fastboot is not an issue .....
It should make your recovery usable. Once done flash any of the oos builds, and before booting flash this same recovery trough twrp and supersu then restart.
You may have done this before, but humor me and do exactly as i asked you to...... Won't hurt.....
Click to expand...
Click to collapse
thanks again.. I believe I have it back now.. factory reset took the encryption password away, infact it took everything away as my device is now wiped completely clean but hey at least its usable again..
appreciate the help... if I could hit the thanks button again I would..
bkeaver said:
thanks again.. I believe I have it back now.. factory reset took the encryption password away, infact it took everything away as my device is now wiped completely clean but hey at least its usable again..
appreciate the help... if I could hit the thanks button again I would..
Click to expand...
Click to collapse
Good for you man!
The bootloader is unlocked and TWRP is installed on the phone. First boot into it went fine. There I made backups and wiped some /system, /data, internal storage and cache..
Now I get "The System has been destroyed. Press power button to shotdown."
I can get into fastboot, but not into TWRP. Tried power button up, tried "fastboot reboot recovery", tired "fastboot boot twrp.img". Nothing is working.
I have a full backup, but that won't do me much good if I can't get TWRP to run.
Is there any way to get into TWRP? Any help would be very much appreaciated.
Edit: Got it fixed. Basically just follow this if you ever have the same problem: http://c.mi.com/oc/miuidownload/detail?guide=2
Still don't get why TWRP wouldn't boot. Is recovery dependent on system? Who designs a phone like this? Oh well, only important thing is that it works again.
I would like to try this - I'm in the exact same position as you and having twrp back would be a lifesaver. However mine is the Chinese version and I'm not sure if flashing the global version is smart...
Edit: I'm seeing success, but it flashed in 1 second, which did nothing..
Just flash the stock firmware back by bronging your phone to fastboot mode and using Xiaomi's Flash Tool using a fastboot image for your phone.
Once unbricked you can set it up, reinstall twrp, then rinse and repeat if in cases it happens again when trying a custom ROM.
Check this linkfor a thorough unbricking guide.
Lyves said:
Just flash the stock firmware back by bronging your phone to fastboot mode and using Xiaomi's Flash Tool using a fastboot image for your phone.
Once unbricked you can set it up, reinstall twrp, then rinse and repeat if in cases it happens again when trying a custom ROM.
Check this linkfor a thorough unbricking guide.
Click to expand...
Click to collapse
Yes, have seen that guide but I'm getting flash xbl error on latest versions of the Xiaomi Flash Tool. So right now I'm actually stuck on Fastboot with no way to revive it.
nyvled said:
Yes, have seen that guide but I'm getting flash xbl error on latest versions of the Xiaomi Flash Tool. So right now I'm actually stuck on Fastboot with no way to revive it.
Click to expand...
Click to collapse
Use an older version. That worked for most.
Lyves said:
Use an older version. That worked for most.
Click to expand...
Click to collapse
I've tried a few at random. Most threw xbl error, one just flashed in a second and then nothing happened on the phone.
I'll give it another shot. Thanks for suggesting. :/
hy my friend if you have mi account you have to sighnout and then flash recovery and then go to recovery with vol up and power when you stil in the fastboot
Slowking said:
"The System has been destroyed. Press power button to shotdown."
Edit: Got it fixed....
Click to expand...
Click to collapse
no need to follow that tutorial
just flash vbmeta in fastboot using
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
and u r good to go
Have you tried orange fox recovery