Related
Hi,
After changing my phone's date into the future, my G2 Touch told me there was an update available, so I told it to go ahead and apply it. When the phone rebooted it came up with this message:
E:No signature (218 files)
E:Verification failed
Installation aborted
I have nandroid installed on the phone. At least I think that's what's installed - I haven't played with any ROM stuff since November I think, when I changed the bootloader (I think - if that's what's giving me the option to do a nandroid backup now) and installed the newest T-Mobile G2 ROM.
Should the phone be able to install the OTA update, or will I have to replace the bootloader in order to get the OTA update on there? If I do have to replace the bootloader, will that require a full wipe?
James
Completely the same problem with HTC Hero after European OTA update. It has been rooted while ago (by following instructions from this forum) and now after setting up date in the future and confirming update, phone reboot and I get "Android System recovery" screen with menu and this message bellow it:
Build: CyaanogenMod v1.4 + JF
Finding update package ...
Opening update package ...
Veryfing update package ...
E: No signature (218 files)
E: Verification failed
Installation aborted.
Click to expand...
Click to collapse
I have the same problem (I did not write down the message, so I'm not sure which "Build:" was listed) .
The update fails, the phone reboots and then works under the old build. Under "settings/about phone" there is also no info about the update. Can one force the phone to download the update a second time? Would this help?
Bye
Nick
P.S. I'm running the phone in Germany over e-plus as network provider. The updates was done over a WiFi connection. The phone is not branded - was from the free market and not from a provider.
Hey,
got the same problem. At least I could extract the official OTA-update-zip to publish it here (see attachment)
There also is a "recovery.img" in the update zip, so I guess usually the OTA update will kill custom recovery bootloaders. We could replace the "recovery.img" in the zip with a hacked one before applying the update.
However first we should fix the verification error...
P.S.: Also Germany, not branded, Vodafone Network
Does anyone know if I will lose all my data if I reflash the original recovery.img onto my phone?
As I used flashrec to flash ra-recovery.img I keept all my data. So I don't belive you will lost any of your data except of your actual recovery image.
At last, we can try to flash origianl RUU, but with this we lost all our personal data.
----
I tried it. I installed flasrec.apk using ASTRO and used this app to flash the recovery.img from here mentioned/linked OTA update zip. Afterwards I changed date again and was able to install OTA Update without errors and loosing personal data. Now I'm without nandroid because of changing recovery image. Keep cool at this procedure installing these flashes takes long time in boot process - I was really near an hard reset ...
Flashing the original recovery.img should not be a problem.
However, I don't want to lose root access, and thus I will wait for the official HTC 2.1-update (hoping someone publishes it online) and then flash it by myself..
I don't mind losing root access at this moment (the reason I rooted my phone was to get wifi tethering but never got it working with a mac).
Since I am total noob with android stuff, I would highly appreciate some step by step instructions or link where I can find what to do. Thanks guys.
Hi, I've been trying to install the recovery.img from the update but I get this message with flashrec 1.1.3:
Code:
"Flash FAILED: Could not run command."
I'm using WWE 405.66 flashed with ra-recovery img 1.6.2... and the rom is rooted.
What am I doing wrong?
I can't even install ra-recovery with flashrec now and I have installed ra-recovery 1.6.2 this morning (I was using 1.5)
And yes, I know I'm going to lose ra-recovery.
rseffner said:
As I used flashrec to flash ra-recovery.img I keept all my data. So I don't belive you will lost any of your data except of your actual recovery image.
At last, we can try to flash origianl RUU, but with this we lost all our personal data.
----
I tried it. I installed flasrec.apk using ASTRO and used this app to flash the recovery.img from here mentioned/linked OTA update zip. Afterwards I changed date again and was able to install OTA Update without errors and loosing personal data. Now I'm without nandroid because of changing recovery image. Keep cool at this procedure installing these flashes takes long time in boot process - I was really near an hard reset ...
Click to expand...
Click to collapse
What was the rom you were using when you flashed the official recovery?
alvaritolalala said:
Hi, I've been trying to install the recovery.img from the update but I get this message with flashrec 1.1.3:
Code:
"Flash FAILED: Could not run command."
I'm using WWE 405.66 flashed with ra-recovery img 1.6.2... and the rom is rooted.
What am I doing wrong?
I can't even install ra-recovery with flashrec now and I have installed ra-recovery 1.6.2 this morning (I was using 1.5)
And yes, I know I'm going to lose ra-recovery.
Click to expand...
Click to collapse
Try the following:
- Copy the recovery.img to your SD card
- Turn off the phone, turn it on with Buttons "HOME"+"ONOFF" pressed such that the ra-recovery which you already have starts
- connect to your phone by cable using "adb shell"
- Then with root access you can flash the image by typing "flash_image recovery /sdcard/recovery.img"
This should do it
jamesots said:
Hi,
After changing my phone's date into the future, my G2 Touch told me there was an update available, so I told it to go ahead and apply it. When the phone rebooted it came up with this message:
E:No signature (218 files)
E:Verification failed
Installation aborted
I have nandroid installed on the phone. At least I think that's what's installed - I haven't played with any ROM stuff since November I think, when I changed the bootloader (I think - if that's what's giving me the option to do a nandroid backup now) and installed the newest T-Mobile G2 ROM.
Should the phone be able to install the OTA update, or will I have to replace the bootloader in order to get the OTA update on there? If I do have to replace the bootloader, will that require a full wipe?
James
Click to expand...
Click to collapse
hey,
I had same problem
go to All programs--> Recovery Flasher--> Restore backup
then restart and update OTA
Greetings from Zagreb, Croatia
Hey guys.
So, for those of you, who do NOT care about root for now, here's what worked for me:
1.: Download the zip-file with the OTA Update, mentioned on the first page and extract it.
2.: Connect your Hero to your PC and copy the recovery.img from the OTA onto your sdcard. Disconnect from computer.
3.: Boot your phone into the bootloader (Home + PWR).
EDIT: Now connect the phone to the pc again!
4.: open the command prompt of your pc, navigate to your Android SDK folder. (If it is not installed, download it and make sure you've got the needed drivers. Otherwise: Download them, using the Setup.exe from Android SDK)
5.: Here are the needed commands:
Code:
adb shell
$su
mount -a
flash_image recovery /sdcard/recovery.img
6.: reboot your phone after exitting the command prompt.
7.: Factory reset, reboot again
8.: And well, wait for the update-window again and be happy, now it should work
EDIT 2:
Any questions? Just leave a reply
@Revoluzifer
OK I did exactly as you explained, but having problem with su command:
Code:
C:\sdk\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
/ # su
su
/sbin/sh: su: not found
I know I know, you're going to say my phone is not rooted at all But believe me it was and some apps that require root access are there (screenshot, wifi tether etc.).
I even tried to find su cmd with find:
Code:
C:\sdk\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
/ # su
su
/sbin/sh: su: not found
But got nothing as you can see.
Ideas?
@dinke:
Which bootloader / recovery console is installed?
Means, what do you see, after booting with Home + PWR?
Also try to input $su instead of just su.
But first tell me your "hack" if any
@Revoluzifer
Thanks for quick reply
I see Android system recovery screen, not sure if this is nandroid or what but have this text on the screen with following options:
Android system recovery <2>
Use trackball to highlight;
click to select.
[Home+Back] reboot system now
[Alt+S] apply sdcard:update.zip
[Alt+W] wipe data/factory reset
[Alt+B] nandroid v2.2 backup
[Alt+R] restore latest backup
[Alt+F] repair ext filesystems
-------------------------------
Click to expand...
Click to collapse
And bellow menu there is build ID:
Build: CyanogenMod v1.4 + JF
I don't remember exact procedure that I applied for rooting hero, but I followed instructions from this forum (I can try by searching for exact thread if that may help you).
Edit: I applied root procedure by following instructions on these two links:
http://forum.xda-developers.com/showpost.php?p=4257045
http://forum.xda-developers.com/showthread.php?t=559613
That sounds just perfect
CyanogenMod 1.4 is exactly the same recovery console i have had before.
(Btw, Hero is not officially supported by CM anymore, had a nice discussion yesterday in cyanogen IRC )
So, try to use $su instead of su, that's what I typed and it all worked just great.
But you definitely first booted into bootload and then connected the phone to your pc again?
Tell me if this worked for you, please...
Greetz,
Sven
dinke said:
Code:
C:\sdk\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
/ # su
su
/sbin/sh: su: not found
Click to expand...
Click to collapse
Forget about the "su". You are already root.
(You can see this, as there's a '#' in front)
Just do the mounting and flashing
Oh... You're right, nerdture... didn't see the #
I *think* I've tried mount no matter of missing 'su' cmd and it didn't work either but will try again as soon as I manage to find some cable to connect hero with macbook (no longer nearby windows machine but have sdk installed on mac so should be working as well)
Revoluzifer said:
But you definitely first booted into bootload and then connected the phone to your pc again?
Click to expand...
Click to collapse
Yes
I've managed mess up my HDX 8.9 while trying to install TWRP and now the touchscreen doesn't work properly.
I have ADB access and can navigate my tablet using shell commands to simulate keyboard presses, however when I use the touchscreen, it responds on the wrong part of the screen. This makes unlocking manually or selecting anything impossible. Touches still register, but just at the wrong part.
The table was working fine on the same day. I downgraded to 14.3.1.0 with no issue, however when I went to install TWRP I made a fatal mistake, I installed the THOR rom, instead of the Apollo.
After it rebooted, the touchscreen stopped working correctly. I then installed the Apollo TWRP over it using ADB but this didn't install TWRP or fix the issue. I used the commands shown
adb shell
su
dd if=/sdcard/signed-apollo-twrp-2860.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
and it appeared to work, but no blue kindle fire logo or recovery menu when I hold down the + button.
I then tried to install SafeStrap. This works correctly, but the touchscreen still responds wrong.
Is there something I can do? Oddly enough the works fine and I can select and run apps, get into SuperSU, etc by using ADB keyboard commands.
kirby2000 said:
I've managed mess up my HDX 8.9 while trying to install TWRP and now the touchscreen doesn't work properly.
I have ADB access and can navigate my tablet using shell commands to simulate keyboard presses, however when I use the touchscreen, it responds on the wrong part of the screen. This makes unlocking manually or selecting anything impossible. Touches still register, but just at the wrong part.
The table was working fine on the same day. I downgraded to 14.3.1.0 with no issue, however when I went to install TWRP I made a fatal mistake, I installed the THOR rom, instead of the Apollo.
After it rebooted, the touchscreen stopped working correctly. I then installed the Apollo TWRP over it using ADB but this didn't install TWRP or fix the issue. I used the commands shown
adb shell
su
dd if=/sdcard/signed-apollo-twrp-2860.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
and it appeared to work, but no blue kindle fire logo or recovery menu when I hold down the + button.
I then tried to install SafeStrap. This works correctly, but the touchscreen still responds wrong.
Is there something I can do? Oddly enough the works fine and I can select and run apps, get into SuperSU, etc by using ADB keyboard commands.
Click to expand...
Click to collapse
You may need help from @ggow, he in the past solved similar problem with his Apollo touchscreen ... until (if) he respond, you can read what happened to him here read til post 665, where is link to guide how to solve this problem (IMHO by flashing wrong ROM for Thor you replaced firmware for your Apollo touchscreen - and you need to replace it back with correct touchscreen firmware for Apollo)...
Depending on your computer skills you may or may be not be able to preform that, if not - then ask ggow for help via PM, or maybe someone experienced enough will help you with this - I am only pointing you in the right direction (I hope)...
Thanks for your help. That was the exact issue I had.
I followed the links in the thread and managed to get a copy of the firmware and flasher and it's now working again.
Oddly enough, flashing the correct TWRP still hasn't given me access to it, but I can look into that myself, I'm just glad I have a working touchscreen again!
kirby2000 said:
Thanks for your help. That was the exact issue I had.
I followed the links in the thread and managed to get a copy of the firmware and flasher and it's now working again.
Oddly enough, flashing the correct TWRP still hasn't given me access to it, but I can look into that myself, I'm just glad I have a working touchscreen again!
Click to expand...
Click to collapse
Well done, but be careful, be sure you have working bootable system, if you can't enter recovery or boot into rom and you don't have unlocked bootloader, your options to recover from some mistakes are very close to ZERO...
kirby2000 said:
Thanks for your help. That was the exact issue I had.
I followed the links in the thread and managed to get a copy of the firmware and flasher and it's now working again.
Oddly enough, flashing the correct TWRP still hasn't given me access to it, but I can look into that myself, I'm just glad I have a working touchscreen again!
Click to expand...
Click to collapse
sorry to bother you , i still flash the wrong aboot and twrp. my touchscreen play himselfe.i can't follow @ggow , because adb say "unauthorized" in twrp,should i choose another twrp?
s7zhong said:
sorry to bother you , i still flash the wrong aboot and twrp. my touchscreen play himselfe.i can't follow @ggow , because adb say "unauthorized" in twrp,should i choose another twrp?
Click to expand...
Click to collapse
Thx a lot! @ggow @kirby2000
i had fix this problem!
we do not need to reboot into recovery , that we could flash the fix img in normal system with the root permission.
just Flash the firmware
Code:
./synaptics_fw_updater -v -f -b Synaptics.3.B.apollo.img
s7zhong said:
Thx a lot! @ggow @kirby2000
i had fix this problem!
we do not need to reboot into recovery , that we could flash the fix img in normal system with the root permission.
just Flash the firmware
Code:
./synaptics_fw_updater -v -f -b Synaptics.3.B.apollo.img
Click to expand...
Click to collapse
It's the same problem to my HD8.9.
I tried it, but
apollo:/data # ./synaptics_fw_updater -v -f -b Synaptics.3.B.apollo.img
./synaptics_fw_updater[7]: syntax error: 'newline' unexpected
I got "synaptics_fw_updater" & "Synaptics.3.B.apollo.img" here.
the AFH link is invalid.
Please supply new "Synaptics.3.B.apollo.img" file.
Thanks!
Hi, i was using CM12.1, however I accepted an update and didn't figured out it was a CM13 Release, so when i dirty flashed the CM13 ROM over the CM 12.1 one, i got suspicious about something was wrong (due to the loading apps getting forever to configure)...the problem is that i tried then to patch gapps 6.0 and the recommended firmware to avoid problems but got many errors, then i tried to downgrade, however my TRWP just get stuck on the initial blue screen and just doesn't load, so i read what to do and did a downgrade using ToT back to Stock Verizone Firmware, and then tried to reinstall TWRP, i used ioroot to root my G3, then tried to reinstall TWRP but it always get an error, when the phone reboots to enter download mode it gets stuck in the LG Screen, and just stays there...i tried to enter TWRP like usual but the problem with the initial screen getting frozen is still there. I wanna get back to CM 12.1 but i have no idea how to make my TWRP work again
Hope you can help me out guys. Thanks
ezugaru said:
Hi, i was using CM12.1, however I accepted an update and didn't figured out it was a CM13 Release, so when i dirty flashed the CM13 ROM over the CM 12.1 one, i got suspicious about something was wrong (due to the loading apps getting forever to configure)...the problem is that i tried then to patch gapps 6.0 and the recommended firmware to avoid problems but got many errors, then i tried to downgrade, however my TRWP just get stuck on the initial blue screen and just doesn't load, so i read what to do and did a downgrade using ToT back to Stock Verizone Firmware, and then tried to reinstall TWRP, i used ioroot to root my G3, then tried to reinstall TWRP but it always get an error, when the phone reboots to enter download mode it gets stuck in the LG Screen, and just stays there...i tried to enter TWRP like usual but the problem with the initial screen getting frozen is still there. I wanna get back to CM 12.1 but i have no idea how to make my TWRP work again
Hope you can help me out guys. Thanks
Click to expand...
Click to collapse
I have the exact same problem, except I cannot downgrade at all. I get to the Download mode and nothing happens. The TWRP only gets to the initial TeamWin screen so I can't do anything through that route. I have no GAPPS and it really sucks. Any help would be appreciated
gypsydanger said:
I have the exact same problem, except I cannot downgrade at all. I get to the Download mode and nothing happens. The TWRP only gets to the initial TeamWin screen so I can't do anything through that route. I have no GAPPS and it really sucks. Any help would be appreciated
Click to expand...
Click to collapse
Hi, this is what i used to downgrade : http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
Hope it helps, i'm at the office now, so when i get home I'll check where i got the resources to downgrade since i used my personal computer to do it.
Hey, i got it working now, i accessed the root files froma explorer in my G3, thn looked for the old recovery.img that were there and deleted them, then tried to reinstall it using adb, it shows 0+0 packages send to the phone, but it actually unblock the TWRP.
ezugaru said:
Hey, i got it working now, i accessed the root files froma explorer in my G3, thn looked for the old recovery.img that were there and deleted them, then tried to reinstall it using adb, it shows 0+0 packages send to the phone, but it actually unblock the TWRP.
Click to expand...
Click to collapse
what file explorer did you use and where was it located...I used es file explorer but cannot find that file
gypsydanger said:
what file explorer did you use and where was it located...I used es file explorer but cannot find that file
Click to expand...
Click to collapse
Try with Root Browser, then look for the Root / sdcard path and delete the recovery.img files, in my case there were 3 of them.
ezugaru said:
Try with Root Browser, then look for the Root / sdcard path and delete the recovery.img files, in my case there were 3 of them.
Click to expand...
Click to collapse
I don't have any of those .img files I tried following that guide as well and nothing happened it got to like 4% then said update failed due to an error. any ideas? I just need to get TWRP working again so I can do a clean flash, is there anyway I can reinstall TWRP it was originally installed through goomanager. tried updating there and it just reboots recovery to get stuck on the teamwin splash screen.
gypsydanger said:
I don't have any of those .img files I tried following that guide as well and nothing happened it got to like 4% then said update failed due to an error. any ideas? I just need to get TWRP working again so I can do a clean flash, is there anyway I can reinstall TWRP it was originally installed through goomanager. tried updating there and it just reboots recovery to get stuck on the teamwin splash screen.
Click to expand...
Click to collapse
I did it using the adb minimal tool, just placed the trwp 2.8.6.0 file into the root of sdcard folder, then using adb (phone must be connected to the laptop/pc in ethernet mode to be recognized) i ran
Code:
adb shell
command, after successfull initialize i used
Code:
su
(phone must be rooted to get a working su), and then i just ran the
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
command and the
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
command, during install it says 0+0 files sent, so i think it detects the trwp is already installed but still do something that fix the brick. Hope you can get it working.
ezugaru said:
I did it using the adb minimal tool, just placed the trwp 2.8.6.0 file into the root of sdcard folder, then using adb (phone must be connected to the laptop/pc in ethernet mode to be recognized) i ran
Code:
adb shell
command, after successfull initialize i used
Code:
su
(phone must be rooted to get a working su), and then i just ran the
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
command and the
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
command, during install it says 0+0 files sent, so i think it detects the trwp is already installed but still do something that fix the brick. Hope you can get it working.
Click to expand...
Click to collapse
when I run
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
I get permission denied
any thoughts on that? I still cannot figure this out ugh so much has changed since I have rooted my last phone
gypsydanger said:
when I run
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
I get permission denied
any thoughts on that? I still cannot figure this out ugh so much has changed since I have rooted my last phone
Click to expand...
Click to collapse
Did you give terminal root permissions by issuing the SU command and then granting the permissions on the phone?
[VK810.4G] [altev] [ViKtory810ROM] official LG G Pad 8.3 Lollipop 36B_00 5.0.2
[VK810.4G] [altev] official LG G Pad 8.3 Lollipop 36B_00 5.0.2 DEBLOAT SCRIPTS and copies of all the files they remove
[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my
I don't recall it asking me after entering the su command...it has asked me on the phone at some point tho, anyway to reset that? Ill be trying again on my lunch break. Thanks for the help so far ill keep updating my status.
gypsydanger said:
I don't recall it asking me after entering the su command...it has asked me on the phone at some point tho, anyway to reset that? Ill be trying again on my lunch break. Thanks for the help so far ill keep updating my status.
Click to expand...
Click to collapse
If you're using SuperSU, launch the app and look at the list of apps with both permanantly granted or denied superuser permissions. You can click on an app there to change it. Are you using a local Terminal emulator app? If so, that's what would request SU access when you enter the command, but if you've done SU in Terminal on this ROM installation before and you granted permanent SU permissions for it, it would give it again automatically when you enter the SU command.
If you're using ADB via USB from a PC, and you authorized USB Debugging on the phone prompt when you connected from the PC, and you then enter the SU command through the PC, I'm not sure what app shows up in the SuperSU app.
You're welcome, good luck!
---------- Post added at 08:39 AM ---------- Previous post was at 08:36 AM ----------
gypsydanger said:
I have the exact same problem, except I cannot downgrade at all. I get to the Download mode and nothing happens. The TWRP only gets to the initial TeamWin screen so I can't do anything through that route. I have no GAPPS and it really sucks. Any help would be appreciated
Click to expand...
Click to collapse
By the way, when using Download mode, what tool are you using with it? LG Flash Tool 2014? Did you previously install the Verizon specific LG drivers, reboot the PC, then connect the phone to the PC in Download mode to a USB 2.0 port with the original cable? Check in Device Manager to see if your phone is listed under Modems when your phone is in Download mode? It can take up to 5-10 minutes for the PC to load the driver you previously installed, each time you connect the phone to a different USB 2.0 port.
Sorry if any of this is repeating anything that's already been asked or suggested.
If you can get it to, I'd suggest flashing the 10B KDZ for the easiest to root with the Stump app in brute force mode, and put TWRP on with TWRP Manager.
roirraW "edor" ehT said:
If you're using SuperSU, launch the app and look at the list of apps with both permanantly granted or denied superuser permissions. You can click on an app there to change it. Are you using a local Terminal emulator app? If so, that's what would request SU access when you enter the command, but if you've done SU in Terminal on this ROM installation before and you granted permanent SU permissions for it, it would give it again automatically when you enter the SU command.
If you're using ADB via USB from a PC, and you authorized USB Debugging on the phone prompt when you connected from the PC, and you then enter the SU command through the PC, I'm not sure what app shows up in the SuperSU app.
You're welcome, good luck!
---------- Post added at 08:39 AM ---------- Previous post was at 08:36 AM ----------
By the way, when using Download mode, what tool are you using with it? LG Flash Tool 2014? Did you previously install the Verizon specific LG drivers, reboot the PC, then connect the phone to the PC in Download mode to a USB 2.0 port with the original cable? Check in Device Manager to see if your phone is listed under Modems when your phone is in Download mode? It can take up to 5-10 minutes for the PC to load the driver you previously installed, each time you connect the phone to a different USB 2.0 port.
Sorry if any of this is repeating anything that's already been asked or suggested.
If you can get it to, I'd suggest flashing the 10B KDZ for the easiest to root with the Stump app in brute force mode, and put TWRP on with TWRP Manager.
Click to expand...
Click to collapse
ok so I figured out the permission denied...somehow my root access in dev options got to off I changed it to adb and got this one to work
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
but this one says /sdcard not found...I created the folder and it still says not found.
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
where exactly does the recovery.img need to be located.
I am using LG Flash Tool 2014 and I have installed the specific drivers from lg and I can see my phone correctly in Device Manager. I just keep getting it stopped due to an error, but if I can get recovery working then I should be able to flash a stable CM for now.
gypsydanger said:
ok so I figured out the permission denied...somehow my root access in dev options got to off I changed it to adb and got this one to work
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
but this one says /sdcard not found...I created the folder and it still says not found.
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
where exactly does the recovery.img need to be located.
I am using LG Flash Tool 2014 and I have installed the specific drivers from lg and I can see my phone correctly in Device Manager. I just keep getting it stopped due to an error, but if I can get recovery working then I should be able to flash a stable CM for now.
Click to expand...
Click to collapse
the file goes in the root of storage, not in a folder, as shown in th pic.
if it says sdcard not found, you either entered the command wrong, or there is something wrong with your file system.
fyi, because the first command worked, you literally have no recovery now. thats what it does, empty the partition.
bweN diorD said:
the file goes in the root of storage, not in a folder, as shown in th pic.
if it says sdcard not found, you either entered the command wrong, or there is something wrong with your file system.
fyi, because the first command worked, you literally have no recovery now. thats what it does, empty the partition.
Click to expand...
Click to collapse
ok yes I have no recovery, that is correct...I put the recovery.img in /root and run the 2nd command again and it still says dd: /sdcard/recovery.img: No such file or directory
when I open up ES File Explorer it opens by default to /sdcard and immediately says /sdcard/ not found...if my file directory is messed up how do I go about getting it corrected?
edit: I used flashify and got TWRP back on successfully but it still won't go past teamwin splash screen....am I missing something I'm on cm 13.020151124-nightly-vs985.
is there a specific version of twrp I need for that nightly?
gypsydanger said:
ok yes I have no recovery, that is correct...I put the recovery.img in /root and run the 2nd command again and it still says dd: /sdcard/recovery.img: No such file or directory
when I open up ES File Explorer it opens by default to /sdcard and immediately says /sdcard/ not found...if my file directory is messed up how do I go about getting it corrected?
edit: I used flashify and got TWRP back on successfully but it still won't go past teamwin splash screen....am I missing something I'm on cm 13.020151124-nightly-vs985.
I'm attempting to wipe recovery again and try CWM to see if that will work.
Click to expand...
Click to collapse
unfortunately, i dont know how to fix it.
im betting stock wont flash because of whatever is damaged on your internal card.
i just looked back and noticed this all started with cm13. i have to wonder, how many phones are they going to break before they pull this update until a fix is found.
your is the first that i have come across that broke the internal card, but i have seen quite a few that broke the external.
im not suggesting you try this, as i really dont know what will happen.
as a last resort, you could try to zero out the data partition with dd code.
given the unknown damage to your card, i cant stress enough, this is a last resort, and may brick your phone.
normally, it should react like a factory reset, but if its still unable to use the internal properly afterwards, it very possibly may not boot fully or at all any more.
edit, as far as i know, the newest version is what they are using, but i dont know what that is specifically.
bweN diorD said:
unfortunately, i dont know how to fix it.
im betting stock wont flash because of whatever is damaged on your internal card.
i just looked back and noticed this all started with cm13. i have to wonder, how many phones are they going to break before they pull this update until a fix is found.
your is the first that i have come across that broke the internal card, but i have seen quite a few that broke the external.
im not suggesting you try this, as i really dont know what will happen.
as a last resort, you could try to zero out the data partition with dd code.
given the unknown damage to your card, i cant stress enough, this is a last resort, and may brick your phone.
normally, it should react like a factory reset, but if its still unable to use the internal properly afterwards, it very possibly may not boot fully or at all any more.
edit, as far as i know, the newest version is what they are using, but i dont know what that is specifically.
Click to expand...
Click to collapse
yea that scares me...now that I have made a little progress I'll try reverting to stock again the two ways I have found. I'll keep updating my progress.
gypsydanger said:
yea that scares me...now that I have made a little progress I'll try reverting to stock again the two ways I have found. I'll keep updating my progress.
Click to expand...
Click to collapse
so I have recovery back on my phone but it won't go past splash screen, I can remove recovery to where I have no recovery at all, everytime I put recovery back on from an app like Flashify it is successful but I can't get past the Splash screen of twrp...if i can get twrp or any other recovery on my phone i should be fine that is what is hanging me up...is there another recovery I can use with CM13 other than TWRP so I can try that and if so how do I get it onto my phone, I can't seem to get fastboot to work so help on that might be useful.
when I try the kdz method to revert to stock it fails due to an error...when I try the dll version to revert to stock it sits on waiting for connection, if I unplug the phone it errors out
gypsydanger said:
so I have recovery back on my phone but it won't go past splash screen, I can remove recovery to where I have no recovery at all, everytime I put recovery back on from an app like Flashify it is successful but I can't get past the Splash screen of twrp...if i can get twrp or any other recovery on my phone i should be fine that is what is hanging me up...is there another recovery I can use with CM13 other than TWRP so I can try that and if so how do I get it onto my phone, I can't seem to get fastboot to work so help on that might be useful.
when I try the kdz method to revert to stock it fails due to an error...when I try the dll version to revert to stock it sits on waiting for connection, if I unplug the phone it errors out
Click to expand...
Click to collapse
What error when flashing the KDZ? Most errors in LG Flash Tool 2014 should be totally ignored, just drag the dialog out of your way and don't press any buttons.
roirraW "edor" ehT said:
What error when flashing the KDZ? Most errors in LG Flash Tool 2014 should be totally ignored, just drag the dialog out of your way and don't press any buttons.
Click to expand...
Click to collapse
it says update failed due to an error and you have to hit retry or it does nothing...unless I need to just do nothing.
edit: IT WORKS YAY...all I did was retry and retry (definition of insanity) and the /sdcard just appeared then the dd command worked and I'm in recovery now yayayayayay
edit: edit: I did take out my eternal SD card so I am going to guess and say that that was the problem from the get go...anybody have any thoughts on that??
The issue started with a couple of mistakes on my part from not reading the forums throughly before attempting something new.
Had installed a custom ROM (AOSPA) using TWRP 3.2.1 (v3) available here on xda. Tried to carry out a factory reset on the unit from inside the OS. Apparently this can cause recovery bootloops. I tried wiping all the partitions and flashing a stock (21D) full zip file from recovery. This had no effect. I then read that I could try to enter the commands
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/misc
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/fota
I would not suggest anyone does this. It, however this resulted in the message that the devices was too corrupt to boot (not just the warning of corruption after bootloader unlocking). So I used LGUP and autoprimes (thanks to that well informed gent by the way) Uppercut to be able to flash a KDZ file of stock from download mode. Only that the kdz available for the US unlocked version would not flash (21C) and I had to flash the (21H) of the Brightpoint version. I reasoned that after I installed it I would be able to install TWRP and install the stock ROM (21D) back in recovery. It installed "successfully" but after booting into the OS it now restarts every 30 seconds or so. Not making it terribly functional as you can imagine. I have tried using both full 21D stock zip versions available in this forum by the way. So if anyone has experienced something similar I'd be glad for advice, if not, then thanks for reading my long story.
Alright, here goes.
So one day I was interested in flashing a new custom ROM (Preferably LineageOS) to my Huawei Mate 10 Lite. Long story short, it's now soft bricked. Only TWRP is working.
But, that's not enough information. Here's the fully story.
After realizing I could not get the Bootloader unlock code using the official method, I've tried DCUnlocker. I paid, and got my code.
I've installed HiSuite, 274829 drivers and finally unlocked the Bootloader. Now, the phone said "This device is unlocked and can't be trusted", but it booted fine. YES!
After that, I downloaded LineageOS 15.1 and flashed it. Before flashing it, I formatted everything, wiped cashe, davlick ect... And.. made my biggest mistake.
Not making a nandroid backup (dammit).
Don't ask me why, I thought it would go well (ugh).
Anyways, I flashed it, error 7. Alright, removed the assert lines. Flashed it again, and it worked, but right at the end, another error? It was error 7, again, but a little different.
This time, it said "failed to mount /dev/block/bootdevice/by-name/vendor at /vendor: device or resource busy"
Okay, now I'm starting to get worried. Like, REALLY WORRIED.
It also said it failed to execute a line in the updater script, one of the last lines. But I would not delete it, just in case.
When I tried to boot, nothing. Went back to Google.
At this point, I learned that any Treble ROM will NOT work with Android version of 7.1. shhhiiii
I was on EMUI 5.1 aka 7.0, and this was worrying. At this point, I tried to return to EMUI 5.1, but since there was no backup, well...... To Google we go!
I did not find any stock room that running EMUI 5.1, but only found EMUI 8.0. I did find a stock room on 7.1, but I'm not paying 15 dollars for it. Not about that life.
I tried the dload method, but apparently my sdcard is on FAT32, and because of that I cannot upload the UPDATE.APP to it.
I've also tried eRecovery, but to no avail. "Failed to get package".
So now I'm stuck on a couple of options, and I need help from you, the XDA community.
1) Remove the line that's causing the issue but at the cost of it maybe not working
2) Somehow format the sdcard and somehow upload the update.app to it
3) Somehow update Android's system to Project Treble, although not sure it's possible since there is no OS.
4) ?????????????????
Please, help me. I'm in hell right now.
Try grabbing the required update files from the teammt site, using the huawei update extractor to grab the partitions you need and then manually flashing with fastboot.
I have the mate 10 pro and usually after getting into a bootloop I flash the kernel, system & recovery_ramdisk then everything starts working as it should
No don't do that, if you are on 7.1 do not flash files from an 8.0 rom because there is more to an oem update then the kernel and sys partition.
If you are in twrp you can flash noCheck recovery. Then you can take your update.zip, hw.zip and data.zip (the 3 files you download from firmware finder, newer firmware might only have 2 files do to an updated data structure by huawei) and send commands to install them in the nocheck recovery. This way every partition will be updated to 8.0 base, this is like the erecovery method but better.
I meant for the original rom, not the 8.0 one, probably should have clarified that in my post
Raptorta said:
No don't do that, if you are on 7.1 do not flash files from an 8.0 rom because there is more to an oem update then the kernel and sys partition.
If you are in twrp you can flash noCheck recovery. Then you can take your update.zip, hw.zip and data.zip (the 3 files you download from firmware finder, newer firmware might only have 2 files do to an updated data structure by huawei) and send commands to install them in the nocheck recovery. This way every partition will be updated to 8.0 base, this is like the erecovery method but better.
Click to expand...
Click to collapse
Well, okay.
I have the 7.0 structure of EMUI 5.1, and right now all I have is the update.zip for the 8.0 Oreo filmware of my EXACT model. I don't have hw or data.
So, I have a couple of questions...
From what I understand, you are trying to solve the problem using method 3, making it Oreo based. If so, how do I go about doing that?
Okay, sure, I can flash noCheck, but finding update, hw, and data for my model, let alone the 7.0 version is pretty hard.
Also, when I find it, what exactly do I have to do???
"Send commands to flash the files" whaaaaat??
All I have rn is adb, fastboot, and on my phone I have TWRP, eRecovery (won't work) and the update.app thingy
Maybe I could format the sdcard to ExFAT, move the 8.0 update.app and install it using the dload method?
Okay so whats your exact model number and your region number (Cxxx). Maybe there is something on Firmware finder.
As for the commands:
You can push files to internal memory with ADB, For example if we have all 3 files and no check recovery we could push them with commands (Taken from the EMUI downgrade script cuz im lazy right now, Thanks to @ante0, @Atarii, @dkionline, @frantm, @Last****ingdroid, @mankindtw, @Pretoriano80, @shimp208, @zanooda123)
adb push ZIPS-HERE/update.zip /data/update/HWOTA/update.zip
adb push ZIPS-HERE/update_all_hw.zip /data/update/HWOTA/update_all_hw.zip
adb push ZIPS-HERE/update_data_public.zip /data/update/HWOTA/update_data_public.zip
adb push images/nocheck.img /data/update/nocheck.img
After that we can send shell commands to queue updates into buffer for the recovery so when the device reboots into recovery mode these commands are executed (this is used for official OTA's as well)
adb shell "echo --update_package=/data/update/HWOTA/update.zip > /cache/recovery/command"
adb shell "echo --update_package=/data/update/HWOTA/update_all_hw.zip >> /cache/recovery/command"
adb shell "echo --update_package=/data/update/HWOTA/update_data_public.zip >> /cache/recovery/command"
After this we push our nocheck recovery to the recovery partition overwriting TWRP
adb shell dd if=/data/update/nocheck.img of=/dev/block/bootdevice/by-name/recovery_ramdisk
After this all we have to do is reboot the device to recovery and the buffered commands run, installing the original firmware through the original recovery resulting in a perfect installation of the firmware with partition table overwrites if necessary.
This most might have become a little complicated, but I think this is the best way to update your system.
Raptorta said:
Okay so whats your exact model number and your region number (Cxxx). Maybe there is something on Firmware finder.
As for the commands:
You can push files to internal memory with ADB, For example if we have all 3 files and no check recovery we could push them with commands (Taken from the EMUI downgrade script cuz im lazy right now, Thanks to @ante0, @Atarii, @dkionline, @frantm, @Last****ingdroid, @mankindtw, @Pretoriano80, @shimp208, @zanooda123)
adb push ZIPS-HERE/update.zip /data/update/HWOTA/update.zip
adb push ZIPS-HERE/update_all_hw.zip /data/update/HWOTA/update_all_hw.zip
adb push ZIPS-HERE/update_data_public.zip /data/update/HWOTA/update_data_public.zip
adb push images/nocheck.img /data/update/nocheck.img
After that we can send shell commands to queue updates into buffer for the recovery so when the device reboots into recovery mode these commands are executed (this is used for official OTA's as well)
adb shell "echo --update_package=/data/update/HWOTA/update.zip > /cache/recovery/command"
adb shell "echo --update_package=/data/update/HWOTA/update_all_hw.zip >> /cache/recovery/command"
adb shell "echo --update_package=/data/update/HWOTA/update_data_public.zip >> /cache/recovery/command"
After this we push our nocheck recovery to the recovery partition overwriting TWRP
adb shell dd if=/data/update/nocheck.img of=/dev/block/bootdevice/by-name/recovery_ramdisk
After this all we have to do is reboot the device to recovery and the buffered commands run, installing the original firmware through the original recovery resulting in a perfect installation of the firmware with partition table overwrites if necessary.
This most might have become a little complicated, but I think this is the best way to update your system.
Click to expand...
Click to collapse
Okay, so here goes again.
My exact build number is RNE-L21C432B137, and my region number is +972 (country).
Anyways, by "ZIPS-HERE" what do you mean? This post isn't very well explained. Sure, you did include some major details, but I can't really understand it.
Also, I'm still wondering, is the dload method still a viable option? Thank you!
Okay so you have an rne-l21c432
https://pro-teammt.ru/firmware-database/?firmware_model=Rne-l21c432&firmware_page=0
From here you can download firmwares for your device.
If you want to try the dload method you can but you should look for the exact same firmware (b137) to be safe, format your sdcard and follow the instructions for that method.
But for that you need the stock recovery which you can get by extracting it from the firmware. After that you can flash it the same way you flashed twrp.
Raptorta said:
Okay so you have an rne-l21c432
https://pro-teammt.ru/firmware-database/?firmware_model=Rne-l21c432&firmware_page=0
From here you can download firmwares for your device.
If you want to try the dload method you can but you should look for the exact same firmware (b137) to be safe, format your sdcard and follow the instructions for that method.
But for that you need the stock recovery which you can get by extracting it from the firmware. After that you can flash it the same way you flashed twrp.
Click to expand...
Click to collapse
Okay, could you tell me step by step, what to do?
I'm unable to format sd card. I need a reader.
Right this second, I'm on TWRP. What do I do?
In the site you've linked, I can find 6 versions of the software.
These are the names of it:
RNE-L21C432B137CUSTC432D001 (2.96GB, FullOTA-MF, v: 161084)
RNE-L21C432B137CUSTC432D001 (2.96GB, FullOTA-MF, v: 160963)
RNE-L21C432B137 (2.96GB, FullOTA-MF, v: 134022)
RNE-L21C432B137 (465.45MB, OTA-MF, v: 134021)
RNE-L21C432B137 (465.45MB, OTA-MF, v: 133902)
RNE-L21C432B137 (2.96GB, FullOTA-MF, v: 133901)
I have no idea what "v" stands for.
So, what do I download, and what do I do? Please help.
Also, could you use "English"? Meaning, explain it step by step.
Like, give examples, ect...
EXAMPLE:
Flash the custom rom using TWRP
Example:
Tap LineageOS from the selection menu in "Install" in TWRP
Swipe to install
Thank you so much!
UPDATE: I cannot download anything.
This XML file does not appear to have any style information associated with it. The document tree is shown below.
Literally, every single link I go to, nothing. This site is useless.
Do you have Discord by any chance? Talking via a forum is really inefficient. If so, send me in PM's your discord.