Related
Hello Developers,
I am a HK Version Hero user. My region started the OTA 2.1 update for HERO.
I have already restore my Nanbackup to the first 1.5 backup.
When it finished the download, my phone reboot to the recovery mode and start the update and prompted:
E:No signature (231 files)
E:Verification failed
Installation aborted.
My need rom version should be 2.73.721.91.
Anyway that I can update to the new stock rom?
Thanks for the help !!
I got the link for the first OTA download, but I am a new user I cannot post it out.
Is it I just delete the recovery.img file? and it will work?
Thanks again
hero-err said:
I got the link for the first OTA download, but I am a new user I cannot post it out.
Is it I just delete the recovery.img file? and it will work?
Thanks again
Click to expand...
Click to collapse
No, you'd have to re-sign the zipfile. If a file is added/removed or editted, the hashes don't match anymore and no one will be able to flash it.
Learn how to re-sign, or just upload it @ multishare as-is, and request re-signing of it. Mayb someone will help you out .
just take the recovery img out of the ruu and flash it then try to update.Should work then
I have the same problem. I really didnt understand what you just said..
My file is a .zip and can not be flashed with flashrec.
can you explain better for a n00b like me?
sundrik said:
I have the same problem. I really didnt understand what you just said..
My file is a .zip and can not be flashed with flashrec.
can you explain better for a n00b like me?
Click to expand...
Click to collapse
you don't flash files with flashrec, you flash them from recovery mode.
and just because something is a .zip doesn't mean it can be flashed. it has to be signed with the appropriate update script.
It like this.
I got an OTA for the 2.1. This generated an error when updating. So i thought i just download the file and do it from recovery mode.
Downloaded the file from here: liveimage.htc.com//OTA_Hero_ChungHwa_3.31.751.1_R-2.73.751.13_release048gnt2ecw16ubyr.zip
The link is not active anymore.
But i still get the same error.
I tried to do a factory reset and do the update after that, but without any luck.
I know this is the update for my phone, but i cant do it. And you guys speak about signing the file before, but i dont know how.
Probably same error for topic starter.
to do what i said you have to boot the phone in recovery.take the files out of the update.zip (or if it a RUU go HERE) in the .zip file should be boot.img,recovery.img,userdata.img,system.img,HBOOT and a few others....
Take out the recovery.img
and flash via fastboot (turn phone one holding back)
open cmd window (windows key + r) type cmd
fastboot flash recovery (drag and drop recover.img into cmd window) press enter
Then try updating
I dont get it to work.
I take out the recovery.img
Turn the phone on by holding 'back' while power on. (Screen with three android skaters)
Then i plug in the usb.
The text 'FASTBOOT' change to 'FASTBOOT USB'
Open cmd (windowskey + r and type cmd adn enter)
Drag and drop the recovery.img to command window and press enter.
This makes the DVD burning application on the computer to start and wants to burn the file.
sundrik said:
I dont get it to work.
I take out the recovery.img
Turn the phone on by holding 'back' while power on. (Screen with three android skaters)
Then i plug in the usb.
The text 'FASTBOOT' change to 'FASTBOOT USB'
Open cmd (windowskey + r and type cmd adn enter)
Drag and drop the recovery.img to command window and press enter.
This makes the DVD burning application on the computer to start and wants to burn the file.
Click to expand...
Click to collapse
Maybe you should use fastboot - the program for your pc?
The steps that were told to you were right, but I think you didn't do the last one as you should. Once in the command-line, you have to type "fastboot flash recovery " (yep, there's a space at the end) and then write the path of the recovery image (i.e., if it's in C:\asd\recovery.img, it would be "fastboot flash recovery \asd\recovery.img"), or drag and drop the file to the cmd, and it will write the path.
You know where to get this fastboot program...
I only find this from 2008. Should be a better one with not so much tweaking?
http://forum.xda-developers.com/showthread.php?t=463627
Nope, not really, I use linux.
Thanks for all the help!! I finally upgraded.
I restore to my 1.5 backup and down the update part by part.
I pull out the recovery.img and zip it back and re-sign it, copy to my phone and rename it to Update.zip and flash the first part. Reboot and copy the OTA2 to the phone and also rename it to Update.zip, flash it again. Final reboot, its now the official 2.1 android update. Also the root is still there.
OTA1
Badongo file 23546527
OTA2
Badongo file 23546783
THANKS again!!!
(sorry about the link, they won't let me post it ><)
hero-err said:
Thanks for all the help!! I finally upgraded.
I restore to my 1.5 backup and down the update part by part.
I pull out the recovery.img and zip it back and re-sign it, copy to my phone and rename it to Update.zip and flash the first part. Reboot and copy the OTA2 to the phone and also rename it to Update.zip, flash it again. Final reboot, its now the official 2.1 android update. Also the root is still there.
OTA1
Badongo file 23546527
OTA2
Badongo file 23546783
THANKS again!!!
(sorry about the link, they won't let me post it ><)
Click to expand...
Click to collapse
PM u, thank you.
Could you tell me the Second HK OTA Package filename?
I really need it, if anyone who know it, please tell me.
Thank you very much.
hello, I flashed RUU_Hero_hTC_Asia_HK_WWE_3.34.721.1_R_Radio_63.18. 55.06P_6.35.15.14_release_signed on my taiwaan hero using goldcard and now i cannot flash my RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoD river. . . please help me! it says error - invalid update tool! WTF ... i have used that ruu many times but now it aint working. it strucks at updating signature.
and even the flash recovery software aint working !
hello, I flashed RUU_Hero_hTC_Asia_HK_WWE_3.34.721.1_R_Radio_63.18. 55.06P_6.35.15.14_release_signed on my taiwaan hero using goldcard and now i cannot flash my RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoD river. . . please help me! it says error - invalid update tool! WTF ... i have used that ruu many times but now it aint working. it strucks at updating signature.
and even the flash recovery software aint working !
I think u need to restore it back to your 1.5 backup first.
Thanks for Hero-err.. I have solved my problem too by following his hints ^_^
i dont have flashed recovery so how would i do nandroid restore ?
I'm trying to replace ROM manager with Tenfars via fastboot and it keeps saying error: cannot load d:recovery-en-goapk.img
Any idea what I might be doing wrong? I deleted the system/recovery-sh and am in fastboot now. Thanks for any help.
Phoneguy589 said:
I'm trying to replace ROM manager with Tenfars via fastboot and it keeps saying error: cannot load d:recovery-en-goapk.img
Any idea what I might be doing wrong? I deleted the system/recovery-sh and am in fastboot now. Thanks for any help.
Click to expand...
Click to collapse
where did you save the recovery img?
Phoneguy589 said:
I'm trying to replace ROM manager with Tenfars via fastboot and it keeps saying error: cannot load d:recovery-en-goapk.img
Any idea what I might be doing wrong? I deleted the system/recovery-sh and am in fastboot now. Thanks for any help.
Click to expand...
Click to collapse
Looks like you need to use full path to .img file.
i was getting this error this morning when i went to do this as well
what i did was:
put the 3 files required to utilize fastboot through command prompt (the 2 adb files, and fastboot itself) and the recovery image WITHOUT RENAMING IT into a folder simply called fastboot in C:\
in command prompt i did:
Code:
> cd C:\fastboot
> fastboot devices (to verify my phone was being seen)
> fastboot flash recovery C:\fastboot\recovery-en-goapk-1029.img (or whatever the hell it's called)
and it worked. for some odd reason, it wouldn't go when i renamed the file, or didn't type the EXACT file path to the recovery image..
maybe this will help you?
I have the img file in c:\ Just for the heck of it I also renamed one recovery and placed in c:\atrix. No matter what directory I choose it still says can't load.
c:\fastboot> fastboot flash recovery c:\recovery-en-goapg.img
That looks right to me but not sure what's up.
jakew02 said:
i was getting this error this morning when i went to do this as well
what i did was:
put the 3 files required to utilize fastboot through command prompt (the 2 adb files, and fastboot itself) and the recovery image WITHOUT RENAMING IT into a folder simply called fastboot in C:\
in command prompt i did:
Code:
> cd C:\fastboot
> fastboot devices (to verify my phone was being seen)
> fastboot flash recovery C:\fastboot\recovery-en-goapk-1029.img (or whatever the hell it's called)
and it worked. for some odd reason, it wouldn't go when i renamed the file, or didn't type the EXACT file path to the recovery image..
maybe this will help you?
Click to expand...
Click to collapse
That's what I needed... Thank You! Still learning my way around.
did it work?
Yes it worked. I needed to type in the full line, not just what was told to type in at the beggining of the thread. It's definately a learning thing. I'm trying to decide what ROM I'd like to run now.... I have the 4-5 beta, tried Cherryblur.5 and didn't like it so I went back. Now I have the blur theme but it still seems a little glitchy and the battery issue is annoying. I read that the ROM manager didn't wipe and install properly plus the issue with it not seeing the ext sd card is a problem.
Hello!
I have the Nexus 6P and I have successfully rooted 16 phones over the past 4 years and never had a problem I couldn't fix. Today I made a mess of my new phone.
I had a perfectly working custom ROM with an unlocked boot loader with TWRP (2.8.7.2) installed. I installed some custom soft keys and got into a boot loop. I went and flashed what I thought was the stock ROM according to the website I was following, and I re locked my boot loader like a fool and was going to eventually unlock it.... turns out I was still boot looped.
I have tried:
sideloading 3 different zips, always get the message "cannot read zip" whatever the zip is
I tried changing the names, doing the full names, doing a stock rooted zipped ROM, nothing works.
I have used SkipSoft and Wugs toolkit and I can't flash ANYTHING or transfer files onto the phone unless the bootloader is unlocked.
I have installed the Google drivers multiple times, ADB devices always works, it seems to not be a driver issue because I can do everything else fine.
I have let the phone sit for 35 minutes in bootloop waiting for it to come back online so I can tick that "OEM unlock" button in the settings menu.
I have also done a dozen other things, the problem is nothing I have done or tried allows me to get any ROM or any file onto the device to flash in TWRP.
Help?
ok shot in the dark here. I had a boot loop until I flashed the flashable vendors zip
I got it in this thread:
http://forum.xda-developers.com/nexus-6p/development/rom-pure-nexus-layers-fi-wifi-calling-t3244563
Give it a whirl if you haven't already.
Found this in the Pure Nexus Project thread, so props to them for providing this.
-MotoNexus- said:
Hello!
I have the Nexus 6P and I have successfully rooted 16 phones over the past 4 years and never had a problem I couldn't fix. Today I made a mess of my new phone.
I had a perfectly working custom ROM with an unlocked boot loader with TWRP (2.8.7.2) installed. I installed some custom soft keys and got into a boot loop. I went and flashed what I thought was the stock ROM according to the website I was following, and I re locked my boot loader like a fool and was going to eventually unlock it.... turns out I was still boot looped.
I have tried:
sideloading 3 different zips, always get the message "cannot read zip" whatever the zip is
I tried changing the names, doing the full names, doing a stock rooted zipped ROM, nothing works.
I have used SkipSoft and Wugs toolkit and I can't flash ANYTHING or transfer files onto the phone unless the bootloader is unlocked.
I have installed the Google drivers multiple times, ADB devices always works, it seems to not be a driver issue because I can do everything else fine.
I have let the phone sit for 35 minutes in bootloop waiting for it to come back online so I can tick that "OEM unlock" button in the settings menu.
I have also done a dozen other things, the problem is nothing I have done or tried allows me to get any ROM or any file onto the device to flash in TWRP.
Help?
Click to expand...
Click to collapse
Thanks, the problem is I can't find a way to sideload anything or move a file over. Everything results in a myriad of errors.
tigercranestyle said:
at worst, you would have to invoke the flash-all command via adb once you extracted the couple of times that you have to. directions are on google's factory image site.
may not be the answer that you were looking for, but it always feels great having a clean device to work with. i mean as it stands, you would have to set everything back up on whatever rom anyway if you somehow got out of the problems you were having. you would spend more time doing that instead of just going the factory image route.
toolkits are fun, but learning your way around them is even more so.
Click to expand...
Click to collapse
I'm gonna check the flash all,I've never done that before. I think that would be all the images in the tgz factory image? Anything to get my phone back yeah, I just need it working again.
-UPDATE- I tried the flash all batch in the system image and I tried the flash all batch command and neither work.
Hey man - crazy story - I literally just got done messing with a toolkit and the EXACT same situation happened to me. Locked bootloader, bootloop, everything. What you need to do is do a complete wipe of everything in TWRP so you can access /data from your PC (unless it isn't messed up currently, and you can decrypt within TWRP, I couldn't...) Then, download Cataclysm (maybe something else will work, idk, but I just did it with cataclysm) and bam - it boots, head to developer options and get the box checked.
Stock images didn't work, nothing did... was scared I had a brick. The saving grace for us is that we both got TWRP installed. No more toolkits for me!
Melamunna said:
Hey man - crazy story - I literally just got done messing with a toolkit and the EXACT same situation happened to me. Locked bootloader, bootloop, everything. What you need to do is do a complete wipe of everything in TWRP so you can access /data from your PC (unless it isn't messed up currently, and you can decrypt within TWRP, I couldn't...) Then, download Cataclysm (maybe something else will work, idk, but I just did it with cataclysm) and bam - it boots, head to developer options and get the box checked.
Stock images didn't work, nothing did... was scared I had a brick. The saving grace for us is that we both got TWRP installed. No more toolkits for me!
Click to expand...
Click to collapse
I have already done the advance wipe and the format data, I just tried again and my computer will not read it as storage with MTP enabled.
Thanks though!
tigercranestyle said:
after extracting the tgz file, it should become a tar file. after extracting that tar file, it should become the six files listed below. these files should be in platform-tools to start from scratch.
bootloader-angler-angler-02.45.img
flash-all.bat
flash-all.sh
flash-base.sh
image-angler-mmb29m.zip
radio-angler-angler-02.50.img
once they are, open command line in that directory (platform-tools) and then "flash-all" should work. if it doesn't make sure you post the error that you're getting on your computer so that others can help.
Click to expand...
Click to collapse
I followed all these steps, I unzipped it and everything and put it in my fastboot folder. I still get the "unknown partition "all" " orrr flash is not recognized as an internal or external command, operable program or batch file. In an attempt with desperation I tried opening every version of the batch file, in the tgz and tar and unzipped AND in the fastboot and it all gives the radio img error.
I still do have my fastboot device connected, to my knowledge that means it can't be a driver problem right?
-MotoNexus- said:
I followed all these steps, I unzipped it and everything and put it in my fastboot folder. I still get the "unknown partition "all" " orrr flash is not recognized as an internal or external command, operable program or batch file. In an attempt with desperation I tried opening every version of the batch file, in the tgz and tar and unzipped AND in the fastboot and it all gives the radio img error.
I still do have my fastboot device connected, to my knowledge that means it can't be a driver problem right?
Click to expand...
Click to collapse
You can't flash anything in fastboot with a locked bootloader. The only way you can get your device to work is by using TWRP to flash a rom.
The flash all command doesn't work because the extracted tar file has A zipped folder inside that has to be extracted also with radio and I think recovery zipped up. You have to extract those two files to put them in the tar file and then you might be able to flash all. But as long as you can fastboot devices you should be able to flash all 6 files and have a brand new device.
tigercranestyle said:
sorry for the late reply. not always here.
1. did you unlock the bootloader again before doing all of this?
2. list the files that are in your platform-tools folder.
3. when you executed the "flash-all" command earlier, you did do it with the dash in between flash and all... right? also, you're doing it without the quotation marks, right?
sorry if they seem silly. just never really know.
Click to expand...
Click to collapse
He can't unlock the bootloader without booting into a rom. He needs to use twrp to flash a full system but I am not sure how to help with that when he can't sideload.
just an unrelated question... why did you lock the bootloader again? what was the purpose?
also, as mentioned... locked bootlader, odds arre USB debugging and OEM unlock are also not checked.... afaik, youre in trouble... hopefully someone else can sav you, im out of ideas
akellar said:
You can't flash anything in fastboot with a locked bootloader. The only way you can get your device to work is by using TWRP to flash a rom.
Click to expand...
Click to collapse
Are you telling me that I'm bricked?
I have no way of transfering files to the devices, it won't read as anything to transfer files and ADB won't sideload anything.
tigercranestyle said:
sorry for the late reply. not always here.
1. did you unlock the bootloader again before doing all of this?
2. list the files that are in your platform-tools folder.
3. when you executed the "flash-all" command earlier, you did do it with the dash in between flash and all... right? also, you're doing it without the quotation marks, right?
sorry if they seem silly. just never really know.
Click to expand...
Click to collapse
Neither am I , I just got back from a trip. I have the fastboot exe adb exe mfastboot exe the ADB api files, and the ROMs I tried to sideload along with all the images I pushed to the device.
Originally I had the bootloader unlocked, like I said I was being a fool blindly following a tutorial to get back to stock and I locked it too soon.
Yeah, I tried flash-all flash all and flash flash-all / flash flash all
dontbeweakvato said:
The flash all command doesn't work because the extracted tar file has A zipped folder inside that has to be extracted also with radio and I think recovery zipped up. You have to extract those two files to put them in the tar file and then you might be able to flash all. But as long as you can fastboot devices you should be able to flash all 6 files and have a brand new device.
Click to expand...
Click to collapse
Okay I unzipped that folder and put all the files in the fastboot folder, I still get the same error. The thing that scares me here is I can use the batch file now and it just gives me an error saying it can't flash because it's bootloader is locked.
Soulfly3 said:
just an unrelated question... why did you lock the bootloader again? what was the purpose?
also, as mentioned... locked bootlader, odds arre USB debugging and OEM unlock are also not checked.... afaik, youre in trouble... hopefully someone else can sav you, im out of ideas
Click to expand...
Click to collapse
They are default unchecked, hence the reason I can't unlock the bootloader again. I said it in my first post, I was being a fool following some guide to get back to stock and ******* up a step.
rift999 said:
He can't unlock the bootloader without booting into a rom. He needs to use twrp to flash a full system but I am not sure how to help with that when he can't sideload.
Click to expand...
Click to collapse
Is there not a way to fix the sideload? Or a way to get my computer to read it as a media devices so I can transfer files or something? It's always worked with previous phones but my computer reads the 6P differently. (even when it was working)
Stop trying to fastboot flash anything, it will not work as I've already started multiple times. The only option you have is to get something moved to storage and flash it from twrp.
akellar said:
Stop trying to fastboot flash anything, it will not work as I've already started multiple times. The only option you have is to get something moved to storage and flash it from twrp.
Click to expand...
Click to collapse
I've tried every driver from Google and Nexus 6P, I can't get it to read the MTP for a file transfer, what would you suggest I do? it doesn't show up as my old phones used to in the computers drives.
I have found 0 success with getting a file on through file transfer or ADB push file.
-MotoNexus- said:
I've tried every driver from Google and Nexus 6P, I can't get it to read the MTP for a file transfer, what would you suggest I do? it doesn't show up as my old phones used to in the computers drives.
I have found 0 success with getting a file on through file transfer or ADB push file.
Click to expand...
Click to collapse
Can't help too much personally, but you might give this a shot:
http://forum.xda-developers.com/showpost.php?p=64317181&postcount=20
Sent from my Nexus 6P using XDA Free mobile app
So I just got it............!!!!! I have spent a total of 16 hours with videos, forums and trial and error. When I was going back the 5th around time messing with drivers I turned my ADB driver into a USB composite because I had no idea I could and instantly I was able to file transfer!!!! Problem solved, I have my ROM on now.
Thank you all for your help! I am so sorry I derped at this, I have been doing this a long time and just got sloppy.
I instaled persona78's B600 mod on TWRP 3.0.2-0 and rebooted. Just boot logo. Nothing else. No recovery, no fastboot, nothing. After struggling a bit I mamaged to get into fastboot, but when I run adb command in Windows 8.1 it says "waiting for device" and that's it. I tried several tools and "kits" with more functions, one of them being TWRP.
Please help! Tommorow morning I have a working trip and I extremely need my phone, and in my country it's already 1:00 a.m.
I will be very thankful for any solution and fast response.
Thanks!
XTutorials said:
I instaled persona78's B600 mod on TWRP 3.0.2-0 and rebooted. Just boot logo. Nothing else. No recovery, no fastboot, nothing. After struggling a bit I mamaged to get into fastboot, but when I run adb command in Windows 8.1 it says "waiting for device" and that's it. I tried several tools and "kits" with more functions, one of them being TWRP.
Please help! Tommorow morning I have a working trip and I extremely need my phone, and in my country it's already 1:00 a.m.
I will be very thankful for any solution and fast response.
Thanks!
Click to expand...
Click to collapse
Try flashing it again and yes..
....B600 stays in boot logo for longer
HaiderHady said:
Try flashing it again and yes..
....B600 stays in boot logo for longer
Click to expand...
Click to collapse
I cannot acces NOTHING just fastboot. How I'm going to flash the rom again?
Linux saves phones, that is what I have to say.
Ran adb in windows: <waiting for device>
Ran adb in ubuntu: Revived my phone!
Thank god this phone is fixed, otherwise I couldn't continue my developing on PA
If you are truly in fastboot mode, with the green android dude (his name is Andy) and the white background then the command
fastboot devices
Click to expand...
Click to collapse
should return your device's serial number. Then you can go ahead and flash the 4 needed partions from the stock ROM with fastboot.
First of all, you need the 4 .img files for boot, recovery, cust and system.
You can get these as follows:
On this page you can find all ALE-L21 firmware. Find the latest. The latest FULL firmware for Europe region is C432B602 (Dual SIM) and C432B603 (Single SIM). Download the FULL version (not OTA) and use Huawei Update Extractor to extract boot, recovery, cust, and system as .img files
Open a command window in the folder with the files and rename them accodingly if you wish (e.g. 06.boot.img -> boot.img)
Then you can flash them in fastboot mode like this:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img
Click to expand...
Click to collapse
That last one may take a bit. Then you can do
fastboot reboot
Click to expand...
Click to collapse
JpegXguy said:
If you are truly in fastboot mode, with the green android dude (his name is Andy) and the white background then the command should return your device's serial number. Then you can go ahead and flash the 4 needed partions from the stock ROM with fastboot.
First of all, you need the 4 .img files for boot, recovery, cust and system.
You can get these as follows:
On this page you can find all Huawei firmware. Search (F3 or Ctrl+F) for ALE-L21 and find the latest firmware. (For example, if you search ALE-L21C432 the latest firmware is B600 as of the time of writing this) Download the FULL version (not OTA) and use Huawei Update Extractor to extract boot, recovery, cust, and system as .img files.
Open a command window in the folder with the files and rename them accodingly if you wish (e.g. 06.boot.img -> boot.img)
Then you can flash them in fastboot mode like this:
That last one may take a bit. Then you can do
Click to expand...
Click to collapse
Thanks for the help. But I already fixed my problem.
XTutorials said:
Thanks for the help. But I already fixed my problem.
Click to expand...
Click to collapse
Just in case someone stumbles upon this. I hate when the forum ends abruptly
JpegXguy said:
If you are truly in fastboot mode, with the green android dude (his name is Andy) and the white background then the command should return your device's serial number. Then you can go ahead and flash the 4 needed partions from the stock ROM with fastboot.
First of all, you need the 4 .img files for boot, recovery, cust and system.
You can get these as follows:
On this page you can find all ALE-L21 firmware. Find the latest. The latest FULL firmware for Europe region is C432B602 (Dual SIM) and C432B603 (Single SIM). Download the FULL version (not OTA) and use Huawei Update Extractor to extract boot, recovery, cust, and system as .img files
Open a command window in the folder with the files and rename them accodingly if you wish (e.g. 06.boot.img -> boot.img)
Then you can flash them in fastboot mode like this:
That last one may take a bit. Then you can do
Click to expand...
Click to collapse
it say partition length error please help
I'm 63 years old & could do with some help - trying to flash my Moto G4 but no luck
Hello folks.
I apologise in advance. I thought something was a good idea, and I said to myself I would give it a try and I won't give up, but I have been at this for about 5 hours now and no progress.
I have a Moto G4 which my wife gave about a year ago. I don't like stock Android and want to install Lineage OS onto it. I understand that first I need to:
1. Unlock my bootloader (done)
2. Install ADB Driver Installer onto my Dell (done)
3. Install Minimal ADB and Fastboot onto my Dell (done)
4. Plug my G4 into my Dell using the correct cable. It seems to work as the ADP Driver Installer / APK Installer recognises it as per the image below
https://drive.google.com/open?id=1QZAu9ZrCsKBhUcCofo2bde5aB89v76TB
5. Open up the command promt in the Minimal ADB and Fastboot folder, type adb devices - the device is recognised
6. Here is where the problems start!
(a) At this stage, as soon as I type adb reboot bootloader, the G4 reboots but as it does, it disappears from the ADB Diver Installer / APK Installer!
(b) Soon after when I type fastboot flash recovery twrp.img then nothing is found, no files or directory or anything.
I don't understand what I am doing wrong and am very stuck sadly.
https://drive.google.com/file/d/1zR361DukYrsc923zD2q6Aml3Xr0DVqlj/view?usp=sharing
Would really appreciate some help from you young clever guys!
Thank you.
George.
George425 said:
Hello folks.
I apologise in advance. I thought something was a good idea, and I said to myself I would give it a try and I won't give up, but I have been at this for about 5 hours now and no progress.
I have a Moto G4 which my wife gave about a year ago. I don't like stock Android and want to install Lineage OS onto it. I understand that first I need to:
1. Unlock my bootloader (done)
2. Install ADB Driver Installer onto my Dell (done)
3. Install Minimal ADB and Fastboot onto my Dell (done)
4. Plug my G4 into my Dell using the correct cable. It seems to work as the ADP Driver Installer / APK Installer recognises it as per the image below
https://drive.google.com/open?id=1QZAu9ZrCsKBhUcCofo2bde5aB89v76TB
5. Open up the command promt in the Minimal ADB and Fastboot folder, type adb devices - the device is recognised
6. Here is where the problems start!
(a) At this stage, as soon as I type adb reboot bootloader, the G4 reboots but as it does, it disappears from the ADB Diver Installer / APK Installer!
(b) Soon after when I type fastboot flash recovery twrp.img then nothing is found, no files or directory or anything.
I don't understand what I am doing wrong and am very stuck sadly.
https://drive.google.com/file/d/1zR361DukYrsc923zD2q6Aml3Xr0DVqlj/view?usp=sharing
Would really appreciate some help from you young clever guys!
Thank you.
George.
Click to expand...
Click to collapse
It says no twrp.img in that folder.
Because You renamed it's name to twrp.img.img ?
Try flash with "fastboot flash recovery twrp.img.img"
common file extensions are not shown in name, or while rename, but you added ".img" at last, so it is doubled..
Hello sir,
Copy the twrp file to the folder where ADB is installed. The folder is located in C drive.
Next you can Shift+right click, open powershell/cmd, whichever is there.
Now type in command
" fastboot flash recovery tw" and click tab button. After tab button, click enter.
This should be done when phone is in bootloader mode and connected to laptop/PC.
after the command execution is over, you can reboot to recovery.
First flash Ex kernel and then flash magisk, in THIS ORDER ONLY, OR YOUR PHONE WILL BRICK!
And voila, you have root! Flash anything!
____Mdd said:
It says no twrp.img in that folder.
Because You renamed it's name to twrp.img.img ?
Try flash with "fastboot flash recovery twrp.img.img"
common file extensions are not shown in name, or while rename, but you added ".img" at last, so it is doubled.
Click to expand...
Click to collapse
Thank you for your suggestion. I did exactly as you said, in fact I tried different variations - I changed twrp.img to just twrp, then tried the command fastboot flash recovery twrp.img, nothing and then I changed it back to how it was, twrp.img and tried the command again, this time ending with twrp.img.img and nothing. Result is as shown below (bootloader not found / not signed or corrupted).
https://drive.google.com/open?id=1qMgUDp767Q32c0MmH2Ey17cpEGI75cJS
What shall I try now?
George425 said:
Thank you for your suggestion. I did exactly as you said, in fact I tried different variations - I changed twrp.img to just twrp, then tried the command fastboot flash recovery twrp.img, nothing and then I changed it back to how it was, twrp.img and tried the command again, this time ending with twrp.img.img and nothing. Result is as shown below (bootloader not found / not signed or corrupted).
https://drive.google.com/open?id=1qMgUDp767Q32c0MmH2Ey17cpEGI75cJS
What shall I try now?
Click to expand...
Click to collapse
You flashed it. Reboot into recovery now.
George425 said:
Thank you for your suggestion. I did exactly as you said, in fact I tried different variations - I changed twrp.img to just twrp, then tried the command fastboot flash recovery twrp.img, nothing and then I changed it back to how it was, twrp.img and tried the command again, this time ending with twrp.img.img and nothing. Result is as shown below (bootloader not found / not signed or corrupted).
https://drive.google.com/open?id=1qMgUDp767Q32c0MmH2Ey17cpEGI75cJS
What shall I try now?
Click to expand...
Click to collapse
You've done it! Reboot to recovery!
Lyuu said:
You flashed it. Reboot into recovery now.
Click to expand...
Click to collapse
DhirajKale789 said:
You've done it! Reboot to recovery!
Click to expand...
Click to collapse
Yes you are both absolutely correct thank you for your help! I didn't think it was working!