[Q] Trouble flashing TWRP! - Nexus 4 Q&A, Help & Troubleshooting

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

Related

Can't flash nor boot a custom recovery on my Nexus 4

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

[Q] Nexus won't boot after update.

Hello,
After updating my Nexus 4 the phone won't boot beyond the Google logo.
I tried to hardreset the phone but when I select "Recovery mode" the phone show me the Google logo and just gets stuck there.
Any ideas?
S_Kruis said:
Hello,
After updating my Nexus 4 the phone won't boot beyond the Google logo.
I tried to hardreset the phone but when I select "Recovery mode" the phone show me a the Google logo and just gets stuck there.
Any ideas?
Click to expand...
Click to collapse
Reflash everything with fastboot or just enter the stock recovery and factory reset. You can get there by choosing recovery at the bootloader and then by pressing vol up + power when you see the green logo with the exclamation mark.
lordneopt said:
Reflash everything with fastboot or just enter the stock recovery and factory reset. You can get there by choosing recovery at the bootloader and then by pressing vol up + power when you see the green logo with the exclamation mark.
Click to expand...
Click to collapse
How can i execute either option?
S_Kruis said:
How can i execute either option?
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-4/general/unroot-nexus-4-to-100-stock-complete-t2039162
but use 4.4.2 factory image: https://developers.google.com/android/nexus/images?hl=pt-PT#occamkot49h
C4SCA said:
http://forum.xda-developers.com/nexus-4/general/unroot-nexus-4-to-100-stock-complete-t2039162
but use 4.4.2 factory image: https://developers.google.com/android/nexus/images?hl=pt-PT#occamkot49h
Click to expand...
Click to collapse
When I'm executing "fastboot flash bootloader bootloader-mako-makoz10l.img"
I give me this error:
ako-makoz10l.img
sending 'bootloader' (2188 KB)...
OKAY [ 0.081s]
writing 'bootloader'...
FAILED (remote: not supported in locked device)
finished. total time: 0.083s
Click to expand...
Click to collapse
S_Kruis said:
When I'm executing "fastboot flash bootloader bootloader-mako-makoz10l.img"
I give me this error:
Click to expand...
Click to collapse
You're bootloader is locked. Do a factory reset in the stock recovery
Sent from my Nexus 5 using XDA Free mobile app
Finally I unlocked the bootloader but now i got a error on this command.
"fastboot -w update image-occam-jop40c.zip" the error that I get is this one...
c:\Fastboot\4.2UnrootNexus4>fastboot -w update image-occam-jop40c.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 544032752 bytes
error: update package missing system.img
Click to expand...
Click to collapse
S_Kruis said:
Finally I unlocked the bootloader but now i got a error on this command.
"fastboot -w update image-occam-jop40c.zip" the error that I get is this one...
Click to expand...
Click to collapse
The.sig errors are ok. The failed to allocate error is not. Try to flash just the system.img. fastboot flash system system.img.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
The.sig errors are ok. The failed to allocate error is not. Try to flash just the system.img. fastboot flash system system.img.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Flashing went well but when it boots its stuck a the Google logo.
When I try to get it in Recovery mode I only get Download mode.
Try to flash a custom recovery then and see if it works. If it does try flashing the zip from recovery. On my HTC sometimes flashing from fastboot would result in a bootloop while from recovery it worked perfectly fine.
Sent from my Nexus 4 using XDA Free mobile app

[ROM] [STOCK] KDZ V20L 6.0 H901 T - Mobile

Update V20E 6.0 T - Mobile
H901 - T Mobile
V20e (6.0)
https://drive.google.com/open?id=0B3R77elw9JjNSmVsVjhjbWdLcEU
V20j (6.0)
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW1FRFU652MMA4P3503B0ON/H90120j_00_0712.kdz
V20l (6.0)
http://pkg03.lime.gdms.lge.com/dn/d...1478794859&h=59e2525cdab042c7ac78e39941ad3362
Woww. Thánks for sharing
reachedxyz said:
Woww. Thánks for sharing
Click to expand...
Click to collapse
Bày đặt nói tiếng anh
My question you have this here as ROM we are happy is here as promised. But is it rooted or is it just the official download untouched ?
Sent from my LG-H901 using XDA-Developers mobile app
diamantericos said:
My question you have this here as ROM we are happy is here as promised. But is it rooted or is it just the official download untouched ?[/URL]
Click to expand...
Click to collapse
KDZs are factory firmware files, untouched.
Is it possible to root? Bootloader remains unlocked?
jonsat said:
Is it possible to root? Bootloader remains unlocked?
Click to expand...
Click to collapse
Bootloader can be unlocked. No word on root yet
Do you have to have stock recovery to used the kdz file
I'll wait for the rooted stock version, but I'm sure we'll be seeing it this week!
shawn1 said:
Do you have to have stock recovery to used the kdz file
Click to expand...
Click to collapse
I nand back to a stock build thru twrp. Booted to Android ran LG bridge and it worked fine
Sent from my LG-H901 using XDA-Developers mobile app
shawn1 said:
Do you have to have stock recovery to used the kdz file
Click to expand...
Click to collapse
You need to use LGUP for flashing KDZ:
http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
First of all, flashing this KDZ will re-lock the bootloader. It is important to know because if you want unlocked bootloader, you need to execute "fastboot oem unlock" which will wipe all user data.
Secondly, I am surprised to see that TWRP is no longer working after MM update:
Code:
O:\LG\H901>fastboot boot twrp-2.8.7.1-h901.img
downloading 'boot.img'...
OKAY [ 0.732s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.749s
Same error if I try to flash TWRP as well. Did somebody successfully manage to root this version?
Edit: I've also tried with latest TWRP available from this thread:
http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-updated-twrp-v3-0-1-0-t3350825
Maybe we need a newer build of TWRP based on MM sources?
sikander3786 said:
First of all, flashing this KDZ will re-lock the bootloader. It is important to know because if you want unlocked bootloader, you need to execute "fastboot oem unlock" which will wipe all user data.
Secondly, I am surprised to see that TWRP is no longer working after MM update:
Code:
O:\LG\H901>fastboot boot twrp-2.8.7.1-h901.img
downloading 'boot.img'...
OKAY [ 0.732s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.749s
Same error if I try to flash TWRP as well. Did somebody successfully manage to root this version?
Edit: I've also tried with latest TWRP available from this thread:
http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-updated-twrp-v3-0-1-0-t3350825
Maybe we need a newer build of TWRP based on MM sources?
Click to expand...
Click to collapse
i got that same error when trying to fastboot boot TWRP. however, i then realized that my bootloader had been relocked. i assume you re-unlocked yours tho. i have tons of Google Play music downloaded for offline listening, so i'm trying to see if i can back that up before unlocking.
edit: moving google music to sdcard, will unlock and give it a try later on
YrrchSebor said:
i got that same error when trying to fastboot boot TWRP. however, i then realized that my bootloader had been relocked. i assume you re-unlocked yours tho. i have tons of Google Play music downloaded for offline listening, so i'm trying to see if i can back that up before unlocking.
edit: moving google music to sdcard, will unlock and give it a try later on
Click to expand...
Click to collapse
Yes, I unlocked the bootloader again. As per siraltus' post in the thread linked below, we need a new MM compatible TWRP:
http://forum.xda-developers.com/tmo...recovery-updated-twrp-v3-0-1-0-t3350825/page2
Means no rooting for now.
sikander3786 said:
You need to use LGUP for flashing KDZ:
http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Click to expand...
Click to collapse
LG Flash tool won't work?
Sent from my LG-H901 using XDA-Developers mobile app
SmileBigNow said:
LG Flash tool won't work?
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
No I don't think so. Not with MM KDZ.
sikander3786 said:
First of all, flashing this KDZ will re-lock the bootloader. It is important to know because if you want unlocked bootloader, you need to execute "fastboot oem unlock" which will wipe all user data.
Secondly, I am surprised to see that TWRP is no longer working after MM update:
Code:
O:\LG\H901>fastboot boot twrp-2.8.7.1-h901.img
downloading 'boot.img'...
OKAY [ 0.732s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.749s
Same error if I try to flash TWRP as well. Did somebody successfully manage to root this version?
Edit: I've also tried with latest TWRP available from this thread:
http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-updated-twrp-v3-0-1-0-t3350825
Maybe we need a newer build of TWRP based on MM sources?
Click to expand...
Click to collapse
YrrchSebor said:
i got that same error when trying to fastboot boot TWRP. however, i then realized that my bootloader had been relocked. i assume you re-unlocked yours tho. i have tons of Google Play music downloaded for offline listening, so i'm trying to see if i can back that up before unlocking.
edit: moving google music to sdcard, will unlock and give it a try later on
Click to expand...
Click to collapse
sikander3786 said:
Yes, I unlocked the bootloader again. As per siraltus' post in the thread linked below, we need a new MM compatible TWRP:
http://forum.xda-developers.com/tmo...recovery-updated-twrp-v3-0-1-0-t3350825/page2
Means no rooting for now.
Click to expand...
Click to collapse
BadNews: I hate to be the one to tell you all this, But LG locked some of the fastboot commands... It has nothing to do with TWRP..
you all gota understand that twrp has its own kernel regrdless of what rom you run............. So ROM and Recovery dont tie into eather other..
Nexus 7 did this same thing some time ago.. the fastboot commands are locked up.. LG did the same on the G3 when we figured out how to get around the download mode.........
anyhow, if you even use< fastboot continue >
you will get same error:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot continue
resuming boot...
FAILED (remote: unknown command)
finished. total time: 0.018s
So now, we are all should I say, F----d Up............. I even use my G3 rooting knowledge to gain root... But that method failed tooo, and it uses the download mode come port way..
seems LG though of everything this time around........ But you can count on one thing,, WE WILL HAVE ROOT again.................
We have something the other devices dont have.,. We can unlock our bootloaders.. So, we just gota wait a bit.....................
Eliminater74 said:
BadNews: I hate to be the one to tell you all this, But LG locked some of the fastboot commands... It has nothing to do with TWRP..
you all gota understand that twrp has its own kernel regrdless of what rom you run............. So ROM and Recovery dont tie into eather other..
Nexus 7 did this same thing some time ago.. the fastboot commands are locked up.. LG did the same on the G3 when we figured out how to get around the download mode.........
anyhow, if you even use< fastboot continue >
you will get same error:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot continue
resuming boot...
FAILED (remote: unknown command)
finished. total time: 0.018s
So now, we are all should I say, F----d Up............. I even use my G3 rooting knowledge to gain root... But that method failed tooo, and it uses the download mode come port way..
seems LG though of everything this time around........ But you can count on one thing,, WE WILL HAVE ROOT again.................
We have something the other devices dont have.,. We can unlock our bootloaders.. So, we just gota wait a bit.....................
Click to expand...
Click to collapse
That's bad, real bad.
The first thing most of us will want to know here is if downgrade to 5.1.1 is safe? If yes, which build? I don't think we have many options there.
For rooting, can we try opening the LG Com port using the old 9% method? Maybe then we can try flashing a root injected system image? I am away from PC so can't try this right now. Won't be asking otherwise.
I will wait for a flashable zip. And hope it will have root. Or maybe stick with the Korean Mm port
Sent from my LG-H901 using XDA-Developers mobile app
Yep. Flashable zip is the way to go for now (if it somehow becomes available). I am not sure how to read system dump from a locked-down device and create a Flashable zip.
I will try downgrading to 5.1.1 in the morning.
Just wondering, why allow bootloader unlock if LG and T-Mobile want to lock down everything else?

[NEED HELP] Accidently wiped all with TWRP

Hello, i accidently wiped all with TWRP, and it says no OS installed
Things i tried
Flash with TWRP the original Software - didnt work
ATM im testing when i install a custom rom if it will work
If you have something that would help it would be extremly nice! Thank you <3
DerScheisRaucher said:
Hello, i accidently wiped all with TWRP, and it says no OS installed
Things i tried
Flash with TWRP the original Software - didnt work
ATM im testing when i install a custom rom if it will work
If you have something that would help it would be extremly nice! Thank you <3
Click to expand...
Click to collapse
you tried to flash system.img, boot.img, recovery.img etc? do the bootloader is still unlocked? frp unlocked?
snapdesign said:
you tried to flash system.img, boot.img, recovery.img etc? do the bootloader is still unlocked? frp unlocked?
Click to expand...
Click to collapse
Where ist the System.img or where i can download it?
Bootloader is still unlocked.
Sorry, i dont know that FRP is ^^
DerScheisRaucher said:
Where ist the System.img or where i can download it?
Bootloader is still unlocked.
Sorry, i dont know that FRP is ^^
Click to expand...
Click to collapse
it's in the bootloader screen... try this tutorial http://forum.xda-developers.com/huawei-p8/how-to/guide-how-to-unbrick-huawei-p8-failed-t3260704 100% works...
snapdesign said:
it's in the bootloader screen... try this tutorial http://forum.xda-developers.com/huawei-p8/how-to/guide-how-to-unbrick-huawei-p8-failed-t3260704 100% works...
Click to expand...
Click to collapse
I think i dont make it right
At fastboot erase cache it gives me a error
Im googling but i will ask you if you know what i should do
erasing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.002s
DerScheisRaucher said:
I think i dont make it right
At fastboot erase cache it gives me a error
Im googling but i will ask you if you know what i should do
erasing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.002s
Click to expand...
Click to collapse
well please reboot to bootloader and tell me what you see there...bootloader unlocked and frp....?
snapdesign said:
well please reboot to bootloader and tell me what you see there...bootloader unlocked and frp....?
Click to expand...
Click to collapse
I see Huawei Logo and powered by android not more
Bootloader Unlocked
Dont know what FRP is ^^
DerScheisRaucher said:
I see Huawei Logo and powered by android not more
Bootloader Unlocked
Dont know what FRP is ^^
Click to expand...
Click to collapse
id you have frp locked the device is bricked...please reboot to bootloader with volume down+power... and don't do anything, please keep twrp
snapdesign said:
id you have frp locked the device is bricked...please reboot to bootloader with volume down+power... and don't do anything, please keep twrp
Click to expand...
Click to collapse
Ok, im in Fastboot mode
In Fastboot it says that my device is there
DerScheisRaucher said:
Ok, im in Fastboot mode
In Fastboot it says that my device is there
Click to expand...
Click to collapse
enter this command fastboot oem device-info
edit: what is under "Phone unlocked" on your screen?
snapdesign said:
enter this command fastboot oem device-info
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
FAILED (remote: Command not allowed)
finished. total time: 0.002s
I have an SD Card, should i maybe flash the images with twrp or wouldnt that work ?
DerScheisRaucher said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
FAILED (remote: Command not allowed)
finished. total time: 0.002s
I have an SD Card, should i maybe flash the images with twrp or wouldnt that work ?
Click to expand...
Click to collapse
I think you have FRP locked so you can't flash anything... if you lose twrp i think you will have to go to service... first we have to see the status of FRP
snapdesign said:
I think you have FRP locked so you can't flash anything... if you lose twrp i think you will have to go to service... first we have to see the status of FRP
Click to expand...
Click to collapse
Ok how can i see the Status?
DerScheisRaucher said:
Ok how can i see the Status?
Click to expand...
Click to collapse
when you reboot to bootloader... what do you see on the screen? can you upload a pic?
snapdesign said:
when you reboot to bootloader... what do you see on the screen? can you upload a pic?
Click to expand...
Click to collapse
For Pic you must wait
But if i boot to bootloader i see Huawei logo in middle of screen and under it powered by android
And that for hours it wont go away
DerScheisRaucher said:
For Pic you must wait
But if i boot to bootloader i see Huawei logo in middle of screen and under it powered by android
And that for hours it wont go away
Click to expand...
Click to collapse
that's not bootloader... press volume down + power for 15-20 seconds
snapdesign said:
when you reboot to bootloader... what do you see on the screen? can you upload a pic?
Click to expand...
Click to collapse
I see this: https://www.dc-unlocker.com/huawei-android-phone-frp-unlock
Should i try this?
DerScheisRaucher said:
I see this: https://www.dc-unlocker.com/huawei-android-phone-frp-unlock
Should i try this?
Click to expand...
Click to collapse
i know someone paid and frp was still locked... wait a little to talk to him to see if he succeeded
snapdesign said:
that's not bootloader... press volume down + power for 15-20 seconds
Click to expand...
Click to collapse
Ok if i do this i get into Fastboot & Rescue Mode
Phone Unlocked
DerScheisRaucher said:
Ok if i do this i get into Fastboot & Rescue Mode
Phone Unlocked
Click to expand...
Click to collapse
wait... when you tried to flash the files or when you entered the command... you weren't in fastboot and rescue mode?

Moto Z 8.0 Full firmware [stock][oreo][griffin]

Many thank @erfanoabdi for the link
https://androidfilehost.com/?fid=890278863836283516
extract ROM ,extract file attack ,put all to the same folder, (hold power + volume down to get into bootloader mode) and run file: retail_AS_800.bat ( no need to run commands)
Done.
Hey, thanks for the tool, just few questions, will this relock my device bootloader ? and am i taking the risk to hard brick it ? Do i need to have adb and fastboot installed ?
thanks for this tool and for your time
K1li4n said:
Hey, thanks for the tool, just few questions, will this relock my device bootloader ? and am i taking the risk to hard brick it ? Do i need to have adb and fastboot installed ?
thanks for this tool and for your time
Click to expand...
Click to collapse
No relock anything. No risk to hard brick. If you flash down to 711 and then OTA update,it will. No need adb and fastboot install. Install usb and motorola driver
thanks for the quick answer. no relock, so if something go wrong i would still be able to flash some custom and rsolve the issue , right ?
thuybang said:
Many thank @erfanoabdi for the link
https://androidfilehost.com/?fid=890278863836283516
extract ROM ,extract file attack ,put all to the same folder, (hold power + volume down to get into bootloader mode) and run file: retail_AS_800.bat ( no need to run commands)
Done.
Click to expand...
Click to collapse
Hi, at the end of the batch say
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
So all data will be erased ?
BTW, I ran the process and the phone went back to encrypted mode again, TWRP is not working any more and root access is gone..Any way to revert back ?
K1li4n said:
thanks for the quick answer. no relock, so if something go wrong i would still be able to flash some custom and rsolve the issue , right ?
Click to expand...
Click to collapse
Yes,sure.
[email protected] said:
Hi, at the end of the batch say
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
So all data will be erased ?
BTW, I ran the process and th phone went back to encrypted mode again
Click to expand...
Click to collapse
Yes,it will erese all.
thuybang said:
Yes,it will erese all.
Click to expand...
Click to collapse
And we lose custom recovery and root asscess
my phone reteu dual sim not retail can i flash this rom ?
t_assal said:
my phone reteu dual sim not retail can i flash this rom ?
Click to expand...
Click to collapse
If you unlockbootloader, i can say : yes.
Nice it works to me ,
I just wanted to know if now im stock with unlocked bootloader , so no updates ? Like security updates ?
lima002 said:
Nice it works to me ,
I just wanted to know if now im stock with unlocked bootloader , so no updates ? Like security updates ?
Click to expand...
Click to collapse
Unlock bootloader always get update as normal,guy. . Any update, security,system....
thuybang said:
Unlock bootloader always get update as normal,guy. . Any update, security,system....
Click to expand...
Click to collapse
Cool thanks
Thanx for this, updates working and all.. Only the wifi seems to be be working bad (no internet access, disconnecting) , although could be my connection..
Hi, can I flash 1650-05 retcn Android 7.0 with an unlocked bootloader on this firmware?
it should work on xt1650-03?
btw, my carrier is tefcl but i think that isn't important for flashing
thuybang said:
Many thank @erfanoabdi for the link
https://androidfilehost.com/?fid=890278863836283516
extract ROM ,extract file attack ,put all to the same folder, (hold power + volume down to get into bootloader mode) and run file: retail_AS_800.bat ( no need to run commands)
Done.
Click to expand...
Click to collapse
I try to flash it, but where is error on system.img_sparsechunk.14 flashing..
C:\adb-fastboot-latest\adb-fastboot-latest>fastboot flash system system.img_spar
sechunk.14
target reported max download size of 536870912 bytes
sending 'system' (151532 KB)...
OKAY [ 4.038s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 4.786s
Click to expand...
Click to collapse
And error on erasing DDR
C:\adb-fastboot-latest\adb-fastboot-latest>fastboot erase DDR
erasing 'DDR'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.035s
Click to expand...
Click to collapse
Phone now in boot loop. Can't start, but goes to fastboot.
How to flash it correctly.
mike331967 said:
I try to flash it, but where is error on system.img_sparsechunk.14 flashing..
And error on erasing DDR
Phone now in boot loop. Can't start, but goes to fastboot.
How to flash it correctly.
Click to expand...
Click to collapse
Can you try flash by RSD lite 6.2.4sofware?
thuybang said:
Unlock bootloader always get update as normal,guy. . Any update, security,system....
Click to expand...
Click to collapse
i got notification about security update (patch may 2018) but error while instaling. any solution? please help.
Ceptoz said:
i got notification about security update (patch may 2018) but error while instaling. any solution? please help.
Click to expand...
Click to collapse
Same here.
Help!

Categories

Resources