Related
I never noticed that CWM was different for 1.2 and 1.1. I currently have 1.2 and tired to install CWM which was the wrong one.
When I try to enter recovery, I get a message of " booting recovery kernel image"
I can turn it off and enter into the stock rom no problem.
Any help would be great to how I can undo this and install CWM.
Used the link for CWM from step 1 from this LINK
Thanks very much.
Tap UI Version : 1.2-5699
Kernal - 2.6.32.9-svn4979
Build - FRF91
Here is a link to a .zip I built for you. You will need to have root access for this.
fix-recovery.zip
Download this to your Gtablet and unzip it to /sdcard. Iif you can't make that work, download to your PC and unzip, then transfer the files over to /sdcard. Using a root file manager (I like ES File Explorer), move the file 'flash_image' into /system/bin, overwrite or rename the existing version if there is one, and change the permissions to make it executable (match the other executable files in the /system/bin folder). Then move the file 'cwm5502.img' into /system/etc/recovery (you might have to create the 'recovery' folder). Next, go back to /sdcard and change permissions on 'fixrecovery.sh' to make it executable as well.
Now open Terminal Emulator (install from the Play store or by other means if you don't already have it) and enter the following commands:
Code:
su
sh /mnt/sdcard/fixrecovery.sh
If the second command won't run, bypass the script by running this instead:
Code:
su
/system/bin/flash_image recovery /system/etc/recovery/cwm5502.img
That will install a version of CWM that is compatible with the 1.2 boot loader. Reboot and you should be able to enter the new recovery. Post back if you cannot get this to work for you, and we can try another way. This would be easier if you have ADB installed and working, but I assume most people do not.
Rochey21 said:
I never noticed that CWM was different for 1.2 and 1.1. I currently have 1.2 and tired to install CWM which was the wrong one.
When I try to enter recovery, I get a message of " booting recovery kernel image"
I can turn it off and enter into the stock rom no problem.
Click to expand...
Click to collapse
Since you have the stock VS ROM, you'll have to use nvflash. See this thread.
---------- Post added at 08:05 PM ---------- Previous post was at 08:02 PM ----------
DaggerDave said:
Here is a link to a .zip I built for you. You will need to have root access for this.
...
Click to expand...
Click to collapse
Good try, but, there's no su on stock ROM; and the process to get one correctly installed is slightly involved.
The user will have to resort to nvflash.
rajeevvp said:
Since you have the stock VS ROM, you'll have to use nvflash. See this thread.
---------- Post added at 08:05 PM ---------- Previous post was at 08:02 PM ----------
Good try, but, there's no su on stock ROM; and the process to get one correctly installed is slightly involved.
The user will have to resort to nvflash.
Click to expand...
Click to collapse
Ok thanks, but I can not find the drivers for APX Mode, using Windows vista 32 bit?
Also just to make sure what Files would I need to use. Just want to make sure exactly what to do, and get it right.
Download the TeamDRH_350M_Prep.zip file from this post. It should have both the nVidia APX drivers and CWM-5.5.0.4 for a 1.2 bootloader (in part9.img).
Read the README file for the APX driver installation, but, don't run the NVFlash_gTablet.bat batch file. Instead, just write a new CWM using the commands in the link in my previous post.
EDIT: Note that you cannot install or upgrade the stock VS ROM using CWM. That can only be done using the stock recovery. For everything else, however, you can use CWM.
Feel like a total N00b :crying:
I have the drivers installed for AXB. I have downloads the zip folder with the img files and drivers etc. I renamed this folder to NVFlash for short.
Do I leave this folder on my laptop or put in on the tablet.
Could you please explain a bit more how to use the command window. I open it but cant seem to get it to work.
I have the folder I download unzipped and saved as C:\NVFlash
Not sure how to do step 2
2. Run this command to determine the partition no. of the recovery (SOS) partition--usually, it is 9: Open a CMD.exe window, then change into the directory containing both the nvflash.exe and the bootloader.bin files. Then run:
You have been very helpful thanks again.
Rochey21 said:
Do I leave this folder on my laptop or put in on the tablet.
Click to expand...
Click to collapse
It's meant to be used on an x86 system (desktop, laptop, ...) running Windows or Linux. You can't run .dll and .exe files--Intel binaries--on an ARM tablet, right?
Could you please explain a bit more how to use the command window. I open it but cant seem to get it to work.
I have the folder I download unzipped and saved as C:\NVFlash
Click to expand...
Click to collapse
Change to the directory containing the nvflash executable and bootloader.bin like this (only type in the stuff in bold):
Code:
[I]C:\SOME\PATH[/I]> [B]cd c:\NVFlash[/B] [I]Change to NVFlash directory[/I]
C:\NVFlash> [I] Note the changed prompt[/I] [I]now[/I]
After that, substitute C:\NVFlash\part9.img instead of C:\SOME\PATH\recovery.img in the given command line.
I understand I cant run the files on the tablet, just meant do I need to transfer any files to the tablet during the process or is it all done through the command window.
I have attached the command window. I typed cd c:\NVFlash and the directory changed to NVFlash.
Not sure how I substitute img 9 then?
EDIT* I got the p.txt file. How would I read this file?
Just looking to get CWM running so I can update to a new custom rom.
Rochey21 said:
I understand I cant run the files on the tablet, just meant do I need to transfer any files to the tablet during the process or is it all done through the command window.
Click to expand...
Click to collapse
No need to transfer anything.
EDIT* I got the p.txt file. How would I read this file?
Click to expand...
Click to collapse
Any editor will read that file. Just double-click on the filename.
Just looking to get CWM running so I can update to a new custom rom.
Click to expand...
Click to collapse
Which one?
rajeevvp said:
No need to transfer anything.
Any editor will read that file. Just double-click on the filename.
Which one?
Click to expand...
Click to collapse
JellyBean Smoother Seems to be good?
Sorry which editor would that be? I opened it in wordpad/notepad and it is all just symbols.
Would something like Hex editor read it?
Rochey21 said:
JellyBean Slim Seems to be good?
Click to expand...
Click to collapse
In that case, shut off the tablet; put it back into APX mode using Power and Vol [-]; then double-click the NVFlash_gTablet.bat batch file. It will do all the prep steps (including installing CWM) needed for a Jellybean ROM install. After the tablet boots into CWM, transfer the ROM install zip file onto the tablet and follow the instructions given in the ROM's first post to install the ROM.
Sorry which editor would that be? I hope it in wordpad/notepad and it is all just symbols.
Click to expand...
Click to collapse
Ah! You've got one of the screwey nvflash executables which produce a binary output. Ignore all this, then.
Ok So do I ignore everything or click the NVFlash_gTablet.bat file?
Rochey21 said:
click the NVFlash_gTablet.bat file?
Click to expand...
Click to collapse
Yes.
(Turn the tablet off, then put it back into APX mode again, though. Otherwise, the batch file will error out.)
rajeevvp said:
Yes.
(Turn the tablet off, then put it back into APX mode again, though. Otherwise, the batch file will error out.)
Click to expand...
Click to collapse
Finally :victory:
Thanks very much for all your help.
I have Smoother Bean installed, doesn't seem to be running correctly but il figure that out myself.
Thanks again.
NEITHER MYSELF NOR XDA ARE RESPONSIBLE FOR YOUR PHONE. FLASH AT YOUR OWN RISK
1. Download Root Explorer by Jrummy in the Play store.
2. Download the tether zip attached to this post.
3. Go into Root Explorer and find System folder, find priv-app, inside priv-app long press VZWEntitlementServices.apk and VZWEntitlementServices.odex rename to VZWEntitlementServices.apk.bak and VZWEntitlementServices.odex.bak and back out to first folder.
4. Go to sdcard folder, download and find tether.zip that you downloaded from step 2. Extract the build.prop, copy it and back out to the home folder. enter the system folder. Rename the build.prop that is there to build.prop.bak, then paste the one you extracted from the zip.
5. Long press on the file and hit permissions in the menu. change permissions Owner: Read/Write, Group:Read, Others: Read (should show rw-r--r--)
6. Exit out of root explorer
7. Reboot
8. Check the tether it should work.
9. PROFIT! Thank baby jesus and buy me a beer lol
Topsnake said:
I TAKE NO RESPONSIBILITY FOR YOUR PHONE OR ANY DAMAGE INCURRED FROM APPLYING THIS.
Prerequisites:
Rooted Maxx/Ultra on Kit Kat 19.6.3
You will not be able to do this on stock phones. If you are on Kit Kat 19.6.3 and are stock, there is currently no way to root it.
1. Download Root Explorer by Jrummy in the Play store.
2. Download the tether zip attached to this post.
3. Go into Root Explorer and find System folder, find priv-app, inside priv-app long press VZWEntitlementServices.apk and VZWEntitlementServices.odex rename to VZWEntitlementServices.apk.bak and VZWEntitlementServices.odex.bak and back out to first folder.
4. Go to sdcard folder, download and find tether.zip that you downloaded from step 2. Extract the build.prop, copy it and back out to the home folder. enter the system folder. Delete the build.prop that is there, then paste the one you extracted from the zip.
5. Long press on the file and hit permissions in the menu. change permissions Owner: Read/Write, Group:Read, Others: Read (should show rw-r--r--)
6. Exit out of root explorer
7. Reboot
8. Check the tether it should work.
9. PROFIT! Thank baby jesus and buy me a beer lol
10. Donations are appreciated to TopSnake
Click to expand...
Click to collapse
Any reason why we shouldn't use the Native Tether for Kit Kat 19.5.3 ?? its working fine here on 19.6.3
Jimmy8881 said:
Any reason why we shouldn't use the Native Tether for Kit Kat 19.5.3 ?? its working fine here on 19.6.3
Click to expand...
Click to collapse
Not really. This is just for those that have yet to apply the 19.5.3 Tether. Its also a slightly more simple method.
This is beautiful! Thank you Topsnake so very much!!!
SupremeOverlord said:
This is beautiful! Thank you Topsnake so very much!!!
Click to expand...
Click to collapse
No problem!
Droid Maxx "Developer Edition"
I did this and now my phone turns on and goes to a black screen. Any ideas? I see the unlocked bootloader then it goes black
smooth781 said:
I did this and now my phone turns on and goes to a black screen. Any ideas? I see the unlocked bootloader then it goes black
Click to expand...
Click to collapse
Likely you borked something with the build prop. Did you make a back up before you tried this?
Sent From Droid Ultra
If I helped you, consider hitting thanks.
no of course I was too lazy to do this.I have never had any problems with these things before. I know the phone is on I have it hook to my computer but I have no picture
---------- Post added at 09:34 PM ---------- Previous post was at 09:25 PM ----------
smooth781 said:
no of course I was too lazy to do this.I have never had any problems with these things before. I know the phone is on I have it hook to my computer but I have no picture
Click to expand...
Click to collapse
I did get twrp reinstalled but it does not seem to do much. I can get into it
smooth781 said:
no of course I was too lazy to do this.I have never had any problems with these things before. I know the phone is on I have it hook to my computer but I have no picture
---------- Post added at 09:34 PM ---------- Previous post was at 09:25 PM ----------
I did get twrp reinstalled but it does not seem to do much. I can get into it
Click to expand...
Click to collapse
You need to fxz with save data. You know how to do that I'm sure?
Sent From Droid Ultra
If I helped you, consider hitting thanks.
Caseyk621 said:
You need to fxz with save data. You know how to do that I'm sure?
Sent From Droid Ultra
If I helped you, consider hitting thanks.
Click to expand...
Click to collapse
No I know nothing about it. can you point me in the direction please
smooth781 said:
No I know nothing about it. can you point me in the direction please
Click to expand...
Click to collapse
You know how to use adb and fastboot right. You likely used fastboot to flash TWRP.
Sent From Droid Ultra
If I helped you, consider hitting thanks.
smooth781 said:
No I know nothing about it. can you point me in the direction please
Click to expand...
Click to collapse
I think im doing the right thing to get this working. I am downloading the latest firmware from the fxz people. 800 meg. I am just not sure 100% what to do with it after I get it
Download fxz from here. Extract. Open command prompt in the folder that you extracted to, the one that contains system.img. Then type the command:
fastboot flash system system.img
That should get you back up and running. Then for WiFi tether use this xposed module. (Easier to apply easier to revert for future OTA.)
http://repo.xposed.info/module/com.dym.motoxtether
Sent From Droid Ultra
If I helped you, consider hitting thanks.
---------- Post added at 10:00 PM ---------- Previous post was at 09:59 PM ----------
smooth781 said:
I think im doing the right thing to get this working. I am downloading the latest firmware from the fxz people. 800 meg. I am just not sure 100% what to do with it after I get it
Click to expand...
Click to collapse
Yeah that's the idea!
Sent From Droid Ultra
If I helped you, consider hitting thanks.
I thought everything was going good then I got an error
bootloader sparse image is malformatted
then
remote failure
---------- Post added at 10:12 PM ---------- Previous post was at 10:10 PM ----------
I also saw at the beginning bootloader variable not supported
I aslo just tried the mfastboot command and so far it is going forward. We will see
smooth781 said:
I thought everything was going good then I got an error
bootloader sparse image is malformatted
then
remote failure
---------- Post added at 10:12 PM ---------- Previous post was at 10:10 PM ----------
I also saw at the beginning bootloader variable not supported
I aslo just tried the mfastboot command and so far it is going forward. We will see
Click to expand...
Click to collapse
Crap. Try using mfastboot. Get from here
http://dottech.org/146758/how-to-root-moto-x-on-android-4-4-kitkat-and-flash-twrp-recovery-guide/
Sent From Droid Ultra
If I helped you, consider hitting thanks.
and my phone just booted up. Thanks for pointing me in the right direction. I could not have done it with out help.
smooth781 said:
and my phone just booted up. Thanks for pointing me in the right direction. I could not have done it with out help.
Click to expand...
Click to collapse
What'd you do to get it working?
Sent From Droid Ultra
If I helped you, consider hitting thanks.
Caseyk621 said:
What'd you do to get it working?
Sent From Droid Ultra
If I helped you, consider hitting thanks.
Click to expand...
Click to collapse
When I used the mfastboot instead of fastboot it took right off. I am updating the apps right now on my phone then I will try the wifi you linked above.
smooth781 said:
When I used the mfastboot instead of fastboot it took right off. I am updating the apps right now on my phone then I will try the wifi you linked above.
Click to expand...
Click to collapse
Cool. Glad you got it working. Yeah I'm using the xposed for WiFi tether. Working just fine.
Sent From Droid Ultra
If I helped you, consider hitting thanks.
For those that are now rooted on 19.6.3 remember this exploit
Droid Maxx "Developer Edition"
Hello! I'm pretty new here and I was hoping if someone could help me
My O+ Fab Lite 2.0 is stuck in my boot animation after I installed a new font. I installed a font before that and everything went smoothly. But instead of replacing the default android font (which I think is Roboto if I'm not mistaken), I replaced the Roboto Bold font. I rebooted my phone just like the app asked me to do. Next thing I know my phone is bricked! I used FontFix from JRummyApps to replace the Roboto Bold font. I really hope I can fix this with your help!! Thank you!
!
PatrickJRS said:
Hello! I'm pretty new here and I was hoping if someone could help me
My O+ Fab Lite 2.0 is stuck in my boot animation after I installed a new font. I installed a font before that and everything went smoothly. But instead of replacing the default android font (which I think is Roboto if I'm not mistaken), I replaced the Roboto Bold font. I rebooted my phone just like the app asked me to do. Next thing I know my phone is bricked! I used FontFix from JRummyApps to replace the Roboto Bold font. I really hope I can fix this with your help!! Thank you!
!
Click to expand...
Click to collapse
Been there, I can help you. Do you have a backup of the font? If so we can use adb or terminal to fix. If not, I can give you a copy of mine.
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
Been there, I can help you.. Do you have a backup of the font? If so we can use adb or terminal to fix. If not, I can give you a copy of mine.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Thank you so much! I don't think I have a backup though.
PatrickJRS said:
Thank you so much! I don't think I have a backup though.
Click to expand...
Click to collapse
Ok, I'll upload a copy of mine. (Should be somewhat universal) Do you have adb or a terminal app that you can type commands into?
Sent from my SM-T210 using Tapatalk
RealWelder said:
Ok, I'll upload a copy of mine. (Should be somewhat universal) Do you have adb or a terminal app that you can type commands into?
Sent from my SM-T210 using Tapatalk
Click to expand...
Click to collapse
do you mean like on a pc? if yes, I do have adb.
If you have TWRP or other custom recovery, you can just flash this zip with it.
https://drive.google.com/file/d/0B3XczzpnAnvwbjhxVG1MVWVtQVE/view?usp=drivesdk
If not, you will need to extract the font and we will install it manually.
Sent from my SM-T210 using Tapatalk
RealWelder said:
If you have TWRP or other custom recovery, you can just flash this zip with it.
https://drive.google.com/file/d/0B3XczzpnAnvwbjhxVG1MVWVtQVE/view?usp=drivesdk
If not, you will need to extract the font and we will install it manually.
Sent from my SM-T210 using Tapatalk
Click to expand...
Click to collapse
Sadly, I've been searching for custom recoveries for my device a while back and it seems like there isn't one available. So no :crying: , I don't have a custom recovery.
To install manually:
1.Extract the font
2.Use adb to push the font to /sdcard/ (adb push * /sdcard/) for the * just drag n drop the font into the cmd window
3. Now we will start our shell commands
adb shell
su
mount -o remount,rw /system /system
cd /system/fonts
cp /sdcard/Roboto-Bold.ttf Roboto-Bold.ttf
chmod 0644 Roboto-Bold.ttf
reboot
Sent from my SM-T210 using Tapatalk
RealWelder said:
To install manually:
1.Extract the font
2.Use adb to push the font to /sdcard/ (adb push * /sdcard/) for the * just drag n drop the font into the cmd window
3. Now we will start our shell commands
adb shell
su
mount -o remount,rw /system /system
cd /system/fonts
cp /sdcard/Roboto-Bold.ttf Roboto-Bold.ttf
chmod 0644 Roboto-Bold.ttf
reboot
Sent from my SM-T210 using Tapatalk
Click to expand...
Click to collapse
sorry for the late reply but when I tried to do the first step this is what it said " adb: error: connect failed: no devices/emulators found "
PatrickJRS said:
sorry for the late reply but when I tried to do the first step this is what it said " adb: error: connect failed: no devices/emulators found "
Click to expand...
Click to collapse
You will need to install adb drivers for your device. If you've ever used adb with this device before, you should already have them installed, though.
Also, the phone will have to be doing it's loop for adb to read it. You may also want to try another usb cable.
Sent from my KYOCERA-C6745 using Tapatalk
PatrickJRS said:
sorry for the late reply but when I tried to do the first step this is what it said " adb: error: connect failed: no devices/emulators found "
Click to expand...
Click to collapse
How's it going?
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
How's it going?
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
whoops, sorry there. well uhm.. I researched on how to install drivers and I can't seem to get it working. Maybe I could turn to you for help again?
I'll see if I can find them for you.
Sent from my KYOCERA-C6745 using Tapatalk
---------- Post added at 07:14 PM ---------- Previous post was at 07:09 PM ----------
Try this. http://www.mediafire.com/file/d68cbf3latzv8cb/
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
I'll see if I can find them for you.
Sent from my KYOCERA-C6745 using Tapatalk
---------- Post added at 07:14 PM ---------- Previous post was at 07:09 PM ----------
Try this. http://www.mediafire.com/file/d68cbf3latzv8cb/
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
hmmm why does it say " The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for 32-bit systems. "
PatrickJRS said:
hmmm why does it say " The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for 32-bit systems. "
Click to expand...
Click to collapse
My bad, looking in the zip it is only for 64 bit. I'll keep looking. In the meantime you might get lucky with the Universal Android USB drivers. You should try that and see if you can get adb going.
To test it just type adb devices and if it sees your phone it will show it under List of attached devices.
Sent from my KYOCERA-C6745 using Tapatalk
---------- Post added at 07:41 PM ---------- Previous post was at 07:31 PM ----------
PatrickJRS said:
hmmm why does it say " The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for 32-bit systems. "
Click to expand...
Click to collapse
Is this an MTK device? If so you can download the mtk drivers.
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
My bad, looking in the zip it is only for 64 bit. I'll keep looking. In the meantime you might get lucky with the Universal Android USB drivers. You should try that and see if you can get adb going.
To test it just type adb devices and if it sees your phone it will show it under List of attached devices.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
sorry but what // which one do you mean by Universal Android USB drivers? I just typed in adb devices but I don't see my device under it.
RealWelder said:
My bad, looking in the zip it is only for 64 bit. I'll keep looking. In the meantime you might get lucky with the Universal Android USB drivers. You should try that and see if you can get adb going.
To test it just type adb devices and if it sees your phone it will show it under List of attached devices.
Sent from my KYOCERA-C6745 using Tapatalk
---------- Post added at 07:41 PM ---------- Previous post was at 07:31 PM ----------
Is this an MTK device? If so you can download the mtk drivers.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Not really sure but by what I remember it is an MTK device
PatrickJRS said:
Not really sure but by what I remeber it is an MTK device
Click to expand...
Click to collapse
https://androidmtk.com/download-mtk-usb-all-drivers
Install these, unplug the device, reboot computer, and then plug it back in an try adb devices again.
As soon as we can get adb to recognize it we can fix it.
Sent from my KYOCERA-C6745 using Tapatalk
---------- Post added at 07:54 PM ---------- Previous post was at 07:50 PM ----------
PatrickJRS said:
Not really sure but by what I remember it is an MTK device
Click to expand...
Click to collapse
I just had another thought too. If you can get it to boot into recovery sometimes adb will see it there. I had a Huawei that I did this same thing to with a font, for it I could only get adb to see it in recovery.
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
https://androidmtk.com/download-mtk-usb-all-drivers
Install these, unplug the device, reboot computer, and then plug it back in an try adb devices again.
As soon as we can get adb to recognize it we can fix it.
Sent from my KYOCERA-C6745 using Tapatalk
---------- Post added at 07:54 PM ---------- Previous post was at 07:50 PM ----------
I just had another thought too. If you can get it to boot into recovery sometimes adb will see it there. I had a Huawei that I did this same thing to with a font, for it I could only get adb to see it in recovery.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
man tough luck :crying:
" Install these, unplug the device, reboot computer, and then plug it back in an try adb devices again. " I did exactly what you said but I still can't see my device. I'm not losing hope though! I'll try getting it in recovery mode but I'll do it tomorrow (or later lol) cause it's like 3:00 in the morning here in my country so yeah I need to get some shut eye. talk to ya later I guess! btw thanks for helping me out I obviously don't know much about these lol :laugh::good:
PatrickJRS said:
man tough luck :crying:
" Install these, unplug the device, reboot computer, and then plug it back in an try adb devices again. " I did exactly what you said but I still can't see my device. I'm not losing hope though! I'll try getting it in recovery mode but I'll do it tomorrow (or later lol) cause it's like 3:00 in the morning here in my country so yeah I need to get some shut eye. talk to ya later I guess! btw thanks for helping me out I obviously don't know much about these lol [emoji23]:good:
Click to expand...
Click to collapse
No problem.
Sent from my KYOCERA-C6745 using Tapatalk
I need debrick image for V10 VS990. If anyone having already please upload and share.
Otherwise anyone having 32 or 64gb sd card with OK VS990 can create by sending following command in adb;
dd if=/dev/block/mmcblk0 of=/dev/block/mmcblk1 bs=4096 count=262144
I have dead V10 VS990 which can only be alive with this image so waiting anxiously. Thanks in advance
OR if you are new you can use following in command shell with rooted vs990
adb shell su -c "dd if=/dev/block/mmcblk0 of=/data/local/tmp/temp bs=512 count=524288"
adb shell su -c "chmod 0755 /data/local/tmp/temp"
adb pull /data/local/tmp/temp C:\adbBackup\mmcblk0
adb shell su -c "rm /data/local/tmp/temp"
and compress the adbbackup folder with winrar and upload and share
same here
Pleaaaasssssss this dump file will save my phone and my week.
Good news everyone I used debrick image from this link for my VS990 and it turned on. Try your luck and share feedback.
http://www.kimcloud.net/lg/LG V10/debrick.img/
Also I am attaching QFIL required files for V10. You can try with QFIL DEBRICK METHOD by searching on Google.
My mobile is again dead due to anti roll back, Please share your dumps if above method works for you.
Which debrick img did you use?
That's great news if it works. I ended up fixing mine with a guy who flashes emmc through teamviewer. Works perfectly.
Do you have the person's contact details and price? Did you get the flashed to a vs990?
This link in not working
The link you provided no longer works. Please provide a working link. This image seems the only solution at the moment.
---------- Post added at 02:32 PM ---------- Previous post was at 02:26 PM ----------
Few days ago, I got dump file of every partition from my phone and saved it. These are individual dump files for every partition. How can I change these dump files to a single unbrick img file.
lionel10andy said:
The link you provided no longer works. Please provide a working link. This image seems the only solution at the moment.
---------- Post added at 02:32 PM ---------- Previous post was at 02:26 PM ----------
Few days ago, I got dump file of every partition from my phone and saved it. These are individual dump files for every partition. How can I change these dump files to a single unbrick img file.
Click to expand...
Click to collapse
The link is working dear.
---------- Post added at 07:43 AM ---------- Previous post was at 07:43 AM ----------
lionel10andy said:
The link you provided no longer works. Please provide a working link. This image seems the only solution at the moment.
---------- Post added at 02:32 PM ---------- Previous post was at 02:26 PM ----------
Few days ago, I got dump file of every partition from my phone and saved it. These are individual dump files for every partition. How can I change these dump files to a single unbrick img file.
Click to expand...
Click to collapse
The link is working dear.
need help with my v10
AlphaCSxx20 said:
That's great news if it works. I ended up fixing mine with a guy who flashes emmc through teamviewer. Works perfectly.
Click to expand...
Click to collapse
hi i also own a v10 which i flashed with wrong rom and would appreciate if i can get the team viewer id or contacts of the guy who managed to revive your phone
need help with my v10
AlphaCSxx20 said:
That's great news if it works. I ended up fixing mine with a guy who flashes emmc through teamviewer. Works perfectly.
Click to expand...
Click to collapse
hey can you please share contact details of the guy who flashed yours via teamviewer
abaids said:
Good news everyone I used debrick image from this link for my VS990 and it turned on. Try your luck and share feedback.
http://www.kimcloud.net/lg/LG V10/debrick.img/
Click to expand...
Click to collapse
hi
There are 5 files in this link
Which file did your phone light ???
abaids said:
Also I am attaching QFIL required files for V10. You can try with QFIL DEBRICK METHOD by searching on Google.
Click to expand...
Click to collapse
I don't know how do you use the unbrick files,
is it by writing to SD card , insert the SD card to phone and reboot? I tried in this method but not work
I also tried with QFIL method with your files , not work , the log in QFIL says:
unable to send FireHose NOP, Device is not in FireHose mode
Which file?
abaids said:
Good news everyone I used debrick image from this link for my VS990 and it turned on. Try your luck and share feedback.
Hi which file did you use?
Click to expand...
Click to collapse
Jolbyc said:
abaids said:
Good news everyone I used debrick image from this link for my VS990 and it turned on. Try your luck and share feedback.
Hi which file did you use?
Click to expand...
Click to collapse
can you please share the image
Click to expand...
Click to collapse
abaids said:
My mobile is again dead due to anti roll back, Please share your dumps if above method works for you.
Click to expand...
Click to collapse
You could share the information that I repair your lg v10
link doesn't work!
abaids said:
Good news everyone I used debrick image from this link for my VS990 and it turned on. Try your luck and share feedback.
Click to expand...
Click to collapse
Hi, the link doesn't work!
Sometimes Huawei releases an update package without approving it. For instance, my device (VIE-L29C636) is getting a B382 update, but the update isn't approved for installation. Here's how to update to those update packages.
NOTE: Using this method, you can also safely upgrade your device even if it is rooted, or has some files system partitions altered. (Of course after finished this process, your device will become unrooted and any alteration to the system partitions mentioned below will revert).
Prerequisites:
Your device is already running EMUI 5 (do not attempt this procedure on EMUI 4 ROM, as the partition layout may differ, and the various firmware (modem, sensor hub, etc.) may not compatible.
Unlocked Bootloader AND FRP.
Latest TWRP from OpenKirin (more on that, including download link, click here).
Huawei Update Extractor, for extracting UPDATE.APP.
imgtool, to convert the sparse android image into an ext4 raw image file.
Method:
Download your preferred update package from Firmware Finder app (Make sure to select the one which has 'FullOTA' designation on it. The package doesn't have to be a 'PV' package). Choose 'update.zip' and the other zip that has your region name on it (for instance, on my C636, look for the zip which has 'spcseas' on it's name). I will refer this 2nd zip as 'regional zip'.
Extract the 'UPDATE.APP' from both zip archive.
Using the Update Extractor on a Windows PC, Extract BOOT, SYSTEM, PRODUCT and VENDOR partitions from UPDATE.APP retrieved from 'update.zip', and extract CUST and VERSION from UPDATE.APP retrieved from your regional zip. You should end up with BOOT.IMG, SYSTEM.IMG, PRODUCT.IMG, VENDOR.IMG, CUST.IMG and VERSION.IMG.
Convert PRODUCT.IMG, VENDOR.IMG and VERSION.IMG to an ext4 image using imgtool, for example:
Code:
imgtool PRODUCT.IMG extract
Beware of overwriting the converted image. imgtool is hardcoded to output the converted file to 'extracted/image.img' folder. ALWAYS rename the image.img to something like 'product.ext4.img' after conversion.
Reboot your device to bootloader mode. Flash BOOT.IMG, SYSTEM.IMG and CUST.IMG via fastboot. For example:
Code:
fastboot flash boot BOOT.IMG
Reboot your device to recovery mode. Type
Code:
fastboot reboot
and hold the Vol Up button on your device to enter recovery mode.
Upload the *.ext4.img converted earlier to your device (doesn't matter where, but I recommend using a safe place like '/sdcard', or USB OTG or external micro SD card). you can use 'adb push', MTP or OTG to upload/copy the ext4.img files to your device.
for each *.ext4.img files, flash it to the appropriate named partitions in
Code:
/dev/block/platform/hi_mci.0/by-name/*
. You can use adb shell on your PC, and a command line program called dd on your device. For faster transfer, try to adjusting the block size to 8M. Example commands (execute from adb shell):
Code:
dd if=/sdcard/product.ext4.img bs=8M of=/dev/block/platform/hi_mci.0/by-name/product
dd if=/sdcard/vendor.ext4.img bs=8M of=/dev/block/platform/hi_mci.0/by-name/vendor
dd if=/sdcard/version.ext4.img bs=8M of=/dev/block/platform/hi_mci.0/by-name/version
Exit TWRP (reboot to system), wait for several minutes for the system to build up it's AOT cache, and enjoy your new EMUI 5 with newer security patch, newer kernel and various features and bug fixes .
EDIT: I apologize that IMGTOOL isn't available in binary form for windows. You can try to use Linux virtual machines to run the IMGTOOL. Any modern GNU/Linux distro should be able to run the IMGTOOL.
Be Alert, by follow this so called "Easy Upgrade", you need to full backup of your data. It is because after upgrade, all data will be reset.
jhleo1 said:
Be Alert, by follow this so called "Easy Upgrade", you need to full backup of your data. It is because after upgrade, all data will be reset.
Click to expand...
Click to collapse
In my case (upgrading from VIE-L29C636B370 to B382), it doesn't erase user data at all. And there is no reason it should erase the data.
But as always, backup your data before performing this procedure, in case something goes wrong.
How to extract product version Vendors use imgtool..
syaif fabian said:
How to extract product version Vendors use imgtool..
Click to expand...
Click to collapse
I'm sorry, I forgot to mention that IMGTOOL is only available as binary in GNU/Linux OS. I think you have to use a VM running a GNU/Linux distro to extract product.img, version.img and/or vendor.img using the IMGTOOL.
@jnakoda
Thank you so much my friend. I was in great trouble as my System Update, File Explorer and Huawei ID apps was deleted from phone due to some experiment. I followed your guide and successfully flashed rom again and boom I got all files back.
Now going to experiment this on B382 firmware
And for those who are curious about this, I successfully used this process for 'meafnaf' region on P9 Plus (VIE-L29)
Once again thanks a lot @jnakoda
---------- Post added at 09:15 PM ---------- Previous post was at 09:10 PM ----------
syaif fabian said:
How to extract product version Vendors use imgtool..
Click to expand...
Click to collapse
imgtool is for converting .img files to ext4 raw image files.
To extract files, you need to use "Huawei Update Extractor" which is mentioned in OP.
---------- Post added at 09:20 PM ---------- Previous post was at 09:15 PM ----------
jhleo1 said:
Be Alert, by follow this so called "Easy Upgrade", you need to full backup of your data. It is because after upgrade, all data will be reset.
Click to expand...
Click to collapse
I confirm in my case (reflashing VIE-L29C185B380), data was not removed. But its better to backup your data first.
faakher said:
@jnakoda
Thank you so much my friend. I was in great trouble as my System Update, File Explorer and Huawei ID apps was deleted from phone due to some experiment. I followed your guide and successfully flashed rom again and boom I got all files back.
Now going to experiment this on B382 firmware
And for those who are curious about this, I successfully used this process for 'meafnaf' region on P9 Plus (VIE-L29)
Once again thanks a lot @jnakoda
---------- Post added at 09:15 PM ---------- Previous post was at 09:10 PM ----------
imgtool is for converting .img files to ext4 raw image files.
To extract files, you need to use "Huawei Update Extractor" which is mentioned in OP.
---------- Post added at 09:20 PM ---------- Previous post was at 09:15 PM ----------
I confirm in my case (reflashing VIE-L29C185B380), data was not removed. But its better to backup your data first.
Click to expand...
Click to collapse
Good Evening i had tried the guide but in my VIE-L09 doesn't work. What can i do? Bootloop infinity
This is easier: https://forum.xda-developers.com/p9/development/eva-nocheck-recovery-flash-unapproved-t3705125
Image works on P9 Plus too. Used it for VIE-L09C432B380.
great post, but as a simple user, i have no idea how to do this steps.
i have a p9 plus c605 b361 and rooted, and i cant update to anything
Every time I want to update to a newer version do I need to repeat the steps?
Or I can directly install new updates from finder without confirmation?
maahmd said:
Every time I want to update to a newer version do I need to repeat the steps?
Or I can directly install new updates from finder without confirmation?
Click to expand...
Click to collapse
heeey...anyone here ?!!?
For Windows users, you can use https://github.com/KinglyWayne/simg2img_win (works great).
maahmd said:
Every time I want to update to a newer version do I need to repeat the steps?
Or I can directly install new updates from finder without confirmation?
Click to expand...
Click to collapse
AYahooo said:
For Windows users, you can use https://github.com/KinglyWayne/simg2img_win (works great).
Click to expand...
Click to collapse
what this is ?!
---------- Post added at 06:51 PM ---------- Previous post was at 06:45 PM ----------
Steve2016 said:
This is easier: https://forum.xda-developers.com/p9/development/eva-nocheck-recovery-flash-unapproved-t3705125
Image works on P9 Plus too. Used it for VIE-L09C432B380.
Click to expand...
Click to collapse
What version? EVA L09: eva_l09b391_nocheckrecovery.img, or EVA L19: eva_l19b391_nocheckrecovery.img ??
maahmd said:
What version? EVA L09: eva_l09b391_nocheckrecovery.img, or EVA L19: eva_l19b391_nocheckrecovery.img ??
Click to expand...
Click to collapse
If this Recovery by Atarii really work on VIE too - it's logical that you use for VIE-L09 the L09 version of this recovery
Steve2016 said:
This is easier: https://forum.xda-developers.com/p9/development/eva-nocheck-recovery-flash-unapproved-t3705125
Image works on P9 Plus too. Used it for VIE-L09C432B380.
Click to expand...
Click to collapse
Tecalote said:
If this Recovery by Atarii really work on VIE too - it's logical that you use for VIE-L09 the L09 version of this recovery
Click to expand...
Click to collapse
I know this but I have a version vie-l29c185 So I do not know which version I chose
maahmd said:
I know this but I have a version vie-l29c185 So I do not know which version I chose
Click to expand...
Click to collapse
If you would say earlier which version you have and if you would search a little bit, then you can find L29:
https://forum.xda-developers.com/showpost.php?p=75234976&postcount=62
Tecalote said:
If you would say earlier which version you have and if you would search a little bit, then you can find L29:
https://forum.xda-developers.com/showpost.php?p=75234976&postcount=62
Click to expand...
Click to collapse
i well try this or this now https://forum.xda-developers.com/p9-plus/how-to/easy-upgrade-to-unapproved-emui-5-update-t3649532
maahmd said:
i well try this or this now https://forum.xda-developers.com/p9-plus/how-to/easy-upgrade-to-unapproved-emui-5-update-t3649532
Click to expand...
Click to collapse
Try it with the Link I give you.
There's no risk. If it works is good, if not, nothing will be changed. (only Recovery, which can be changed after)
Tecalote said:
Try it with the Link I give you.
There's no risk. If it works is good, if not, nothing will be changed. (only Recovery, which can be changed after)
Click to expand...
Click to collapse
Ok i will do it now if it does not work ..do you have a download link RECOVRY bised for p9 plus ?
Or I will pull it out of the update file
I'll tell you the result
maahmd said:
Ok i will do it now if it does not work ..do you have a download link RECOVRY bised for p9 plus ?
Or I will pull it out of the update file
I'll tell you the result
Click to expand...
Click to collapse
I don't know what you mean now
Download the Nocheck Recovery for L29 from the Link I give you
https://forum.xda-developers.com/showpost.php?p=75234976&postcount=62
and do the instructions from the OP
https://forum.xda-developers.com/p9/development/eva-nocheck-recovery-flash-unapproved-t3705125
But with the RIGHT Firmware for your VIE-L29 device (3 zips from Firmware Finder /FullOTA)
After updating Firmware Bootloader is closed and Root is gone.
You have to open again (Factoryreset low-level wipe - if it doesn't do 100% do it manually from settings /advanced settings /backup restore /Factoryreset with wipe of internal storage - this is important! ) and flash TWRP and Root again