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!
Related
If you are on MDK, I need really would appreciate one of you to run a script for me and upload it. Im trying to test whether we have the ability to use the sdcard to unbrick S4's like the Note 3 and Galaxy S3 people do. I only thought that this was worth doing since it works on the Note 3. If this works ill write up a guide on how to unbrick your phone without JTAG. Please upload the output. This would be very helpful to know whether we have the ability to unbrick using these means, also it would mean that we would be able to test bootloader unlock ideas without such a high risk of a brick.
Note: For this test you have to have a MDK phone. Later on we can test for ME7, etc.
Open terminal or use adb from a pc:
Edit: see below
If your sdcard is not located at /sdcard please edit the script to your needs, for instance on the s4 your external sdcard is located at /mnt/extSdCard so you could substitute that for /sdcard in the script above. Thanks
I have a MDK phone but I'm running a ME7 rom. Will that work?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Ryno77 said:
I have a MDK phone but I'm running a ME7 rom. Will that work?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yes, but Im going to to edit the script because I don't want it to include any of your personal data, so to fix either go here and download the zip in the bottom of the OP (that creates the debrick.img for you) or you can use one of the modified scripts below (they both say the same thing btw, its just that I forget if terminal/adb uses bytes by default or megabytes). If you do decide to make this, pm the file.
su
dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1024 count=131072 conv=notrunc,noerror
Click to expand...
Click to collapse
su
dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1M count=128 conv=notrunc,noerror
Click to expand...
Click to collapse
If your sdcard is not located at /sdcard please edit the script to your needs, for instance on the s4 your external sdcard is located at /mnt/extSdCard so you could substitute that for /sdcard in the script above.
Surge1223 said:
If you are on MDK, I need really would appreciate one of you to run a script for me and upload it. Im trying to test whether we have the ability to use the sdcard to unbrick S4's like the Note 3 and Galaxy S3 people do. I only thought that this was worth doing since it works on the Note 3. If this works ill write up a guide on how to unbrick your phone without JTAG. Please upload the output. This would be very helpful to know whether we have the ability to unbrick using these means, also it would mean that we would be able to test bootloader unlock ideas without such a high risk of a brick.
Note: For this test you have to have a MDK phone. Later on we can test for ME7, etc.
Open terminal or use adb from a pc:
Edit: see below
If your sdcard is not located at /sdcard please edit the script to your needs, for instance on the s4 your external sdcard is located at /mnt/extSdCard so you could substitute that for /sdcard in the script above. Thanks
Click to expand...
Click to collapse
Uploading now. I'll pm you a link to the file. I'm running aosp right @ the moment on my MDK phone. Hope that doesn't matter.
---------- Post added at 12:04 PM ---------- Previous post was at 11:16 AM ----------
Surge1223 said:
yes, but Im going to to edit the script because I don't want it to include any of your personal data, so to fix either go here and download the zip in the bottom of the OP (that creates the debrick.img for you) or you can use one of the modified scripts below (they both say the same thing btw, its just that I forget if terminal/adb uses bytes by default or megabytes). If you do decide to make this, pm the file.
If your sdcard is not located at /sdcard please edit the script to your needs, for instance on the s4 your external sdcard is located at /mnt/extSdCard so you could substitute that for /sdcard in the script above.
Click to expand...
Click to collapse
PM Sent.
I'll keep you guys updated. From what I hear this *should* work on Qualcomm variant S4's. So far, no dice, but I believe some of that is user error. Alot of this is writing the right partitions to right areas, with the right block sizes etc, etc, etc. Thanks guys.
Surge1223 said:
I'll keep you guys updated. From what I hear this *should* work on Qualcomm variant S4's. So far, no dice, but I believe some of that is user error. Alot of this is writing the right partitions to right areas, with the right block sizes etc, etc, etc. Thanks guys.
Click to expand...
Click to collapse
Glad to help when I can. Hope you find what you're looking for. Thanks for working on this.
Sent from my SCH-I545 using XDA Premium 4 mobile app
So if this works... Then hypothetically we could restore the MDK bootkoader if unfortunate enough to have ended up on ME7 version. Or am I misunderstanding the possibilities here?
Sent from my SCH-I545 using xda app-developers app
No this wouldnt let you downgrade, just save you from having to use jtag in case you brick. But Ive tried three different mdk unbrick.img's (my own and two from others) and havent had success.
Sent from my XT912 using xda app-developers app
My S4 Sch-i545 is hardbricked
any luck on getting a debrick image to boot a hard bricked s4 from Verizon?
arrowproof said:
any luck on getting a debrick image to boot a hard bricked s4 from Verizon?
Click to expand...
Click to collapse
Kind of, but not to the point of unbricking entirely. Im testing a alternative debrick method as we speak for MDK. If you want to test/need to test one out I can upload instructions and files. The debrick image has the gpt and partition info, it also contains the bootloaders for MDK.
Surge1223 said:
Kind of, but not to the point of unbricking entirely. Im testing a alternative debrick method as we speak for MDK. If you want to test/need to test one out I can upload instructions and files. The debrick image has the gpt and partition info, it also contains the bootloaders for MDK.
Click to expand...
Click to collapse
yes it would be nice if you can upload those files. Thanks
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"
Any suggestions on what I can do to fix this?
londonandlawson said:
Any suggestions on what I can do to fix this?
Click to expand...
Click to collapse
If you can boot into TWRP, you can ADB push a ROM or recovery file from your PC.
I have the stock software on my pc, a .tgz file i downloaded. Would you care to link me to instructions on what to do?
londonandlawson said:
I have the stock software on my pc, a .tgz file i downloaded. Would you care to link me to instructions on what to do?
Click to expand...
Click to collapse
You have some homework. Start by reading this and asking questions in that thread. You will eventually recover your device, but not going to happen tomorrow. This is a good learning exercise.
Go here >http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
I have the C:\\adb folder setup, I just wanted to make sure I had the right commands to use
londonandlawson said:
I have the C:\\adb folder setup, I just wanted to make sure I had the right commands to use
Click to expand...
Click to collapse
So you will want to download a custom ROM from Android Development section. Put it in the same folder as ADB and fastboot. Then use the ADB command to push that .zip file to your N6. Syntax of the command is critical. I'd suggest googling ADB push and read several different threads. Here's one to start with >http://forum.xda-developers.com/showthread.php?t=1601802&page=4
---------- Post added at 08:09 PM ---------- Previous post was at 07:48 PM ----------
londonandlawson said:
Any suggestions on what I can do to fix this?
Click to expand...
Click to collapse
One other point: are you sure you have drivers loaded on your PC, and your PC can see your N9?
---------- Post added at 08:14 PM ---------- Previous post was at 08:09 PM ----------
londonandlawson said:
Any suggestions on what I can do to fix this?
Click to expand...
Click to collapse
Since you are trying to connect your N9 to your PC while booted to TWRP, you may need to uninstall and reinstall drivers, IF your PC can't see your N9.
got it going
londonandlawson said:
got it going
Click to expand...
Click to collapse
Great news! Care to share for other users?
I just downloaded the factory image and unzipped it in the C://adb folder then held shift-right click in that folder to open a new command window. From there I did the commands to install the recovery, system image and kernel
NOTE-1:
I'm not a developer or something even near to that. All information provided here is copied from different internet sources and according to best of my knowledge.
I have created this flashable zip myself and tried this on QMobile Z8 only. It's similar to Wiko Ridge 4G and Blu Life One (2015) in hardware specifications.
I'll not be responsible for any harm to you or your device. It works perfectly for me. You may try it on your own risk.
Save / backup your data before continuing.
NOTE-2:
This flashable zip flashes SYSTEM and BOOT partitions only. If you face ROM abnormal behavior like signals issue, charging problem, device heat up etc. you may flash other partitions as explained here.
Read here more about partitions.
REQUIREMENTS
To flash zip, CUSTOM RECOVERY must be installed. If you don't have one, get here.
If your device is bricked and doesn't boot, try flashing factory firmware as explained here. Even if Download Mode isn't accessible, get official support for your device and pray for it.
STEPS
Download QMobile Z8 Stock ROM Lollipop 5.0.2 Rooted flashable unsigned zip and place it on SD Card or Internal Memory (if you don't going to wipe it).
Reboot into Recovery.
Install ROM zip.
Wipe DALVIK-CACHE, CACHE & DATA.
Reboot. Ignore "No OS Installed" warning (if it comes).
Enjoy!
Thanks for Your Post
I have Qmobile z8 , i updated the firmware of Wiko Ridge 4g on my phone few days before.
So my current OS is Ridge 4g , now as i have tried to install your custom rom you mentioned in this thread
it goes normally about 25 percent in progress bar then suddenly progress bar completed as it goes completed , there is no error but in bottom its written Done. then i clear cache and then restart the phone , but it stuck on Wicko logo then restart and this continues. It seems installation did not go completed ,,,, Any solution ?
sadiq1 said:
I have Qmobile z8 , i updated the firmware of Wiko Ridge 4g on my phone few days before.
So my current OS is Ridge 4g , now as i have tried to install your custom rom you mentioned in this thread
it goes normally about 25 percent in progress bar then suddenly progress bar completed as it goes completed , there is no error but in bottom its written Done. then i clear cache and then restart the phone , but it stuck on Wicko logo then restart and this continues. It seems installation did not go completed ,,,, Any solution ?
Click to expand...
Click to collapse
Flashable zip contains just system.img and boot.img. Extract both files and flash using dd.
What is dd , can you please explain what to do in some detail , i am not so much familiar with android
sadiq1 said:
What is dd , can you please explain what to do in some detail , i am not so much familiar with android
Click to expand...
Click to collapse
dd is a command on UNIX-like operating systems including Linux and Android to copy / dump data. https://www.computerhope.com/unix/dd.htm
Put both img files on internal sd card. Boot in recovery and run these commands from built-in terminal or adb shell:
Code:
cd /sdcard
dd if=boot.img of=/dev/block/mmcblk0p23
dd if=system.img of=/dev/block/mmcblk0p24
Make sure "/dev/block/mmcblk0p23" and "/dev/block/mmcblk0p24" are correct partitions to flash or you may overwrite wrong partitions.
Don't forget to make a backup before making experiments.
mirfatif said:
Flashable zip contains just system.img and boot.img. Extract both files and flash using dd.
Click to expand...
Click to collapse
This method of creating a .img using DD is quite difficult so consider doing this instead:
download mode in noir z8
turn off your phone
press*volume +,vol -*and*power button*for 5 second then download mode mn aa jae ga
Firmware to be downloaded from here
http://de.wikomobile.com/maj.php?telephone=549
Rest info is in the pics attached below serial wise
Hit the thumbs up to support me and reply if you need further assistance
x.ak**** said:
This method of creating a .img using DD is quite difficult so consider doing this instead:
download mode in noir z8
turn off your phone
press*volume +,vol -*and*power button*for 5 second then download mode mn aa jae ga
Firmware to be downloaded from here
http://de.wikomobile.com/maj.php?telephone=549
Rest info is in the pics attached below serial wise
Hit the thumbs up to support me and reply if you need further assistance
Click to expand...
Click to collapse
That's for flashing stock firmware. https://forum.xda-developers.com/android/help/factory-firmware-qmobile-z8-wiko-ridge-t3586572
Mine flashable image is a bit modified, rooted, bloats removed etc. But yes flashers are easy to use and risk-free.
mirfatif said:
That's for flashing stock firmware. https://forum.xda-developers.com/android/help/factory-firmware-qmobile-z8-wiko-ridge-t3586572
Mine flashable image is a bit modified, rooted, bloats removed etc. But yes flashers are easy to use and risk-free.
Click to expand...
Click to collapse
Exactly that's why I prefer them and recommend them.
I have already used the firmware method from Wiko site ,
but my Wifi and bluetooth are not working
---------- Post added at 05:44 PM ---------- Previous post was at 05:41 PM ----------
mirfAtif
where can i write this command
cd /sdcard
dd if=boot.img of=/dev/block/mmcblk0p23
dd if=system.img of=/dev/block/mmcblk0p24
I have TWRP this is a GUI program , where can i write command there?
---------- Post added at 06:35 PM ---------- Previous post was at 05:44 PM ----------
I found the terminal to write the command
Let me know where should i keep the files after unzip them
---------- Post added at 06:46 PM ---------- Previous post was at 06:35 PM ----------
Sorry mirfatif
You told me every thing in ur first post , i didnt read it properly,
Thanks ,
Just let me know is there any way to find out which partition is for System and which is for Boot on my phone
sadiq1 said:
Just let me know is there any way to find out which partition is for System and which is for Boot on my phone
Click to expand...
Click to collapse
Execute these commands:
Code:
ls -l /dev/block/bootdevice/by-name/boot
ls -l /dev/block/bootdevice/by-name/system
sadiq1 said:
I have already used the firmware method from Wiko site ,
but my Wifi and bluetooth are not working
Click to expand...
Click to collapse
Flash QMobile factory firmware, not Wiko's. If that doesn't fix, there must be hardware problem.
Atif
I tried to copy both files.
on first file its copied 32 mb with no error
on second file it only copied 32 mb and said no space left on device
what its mean , but my device has space
sadiq1 said:
Atif
I tried to copy both files.
on first file its copied 32 mb with no error
on second file it only copied 32 mb and said no space left on device
what its mean , but my device has space
Click to expand...
Click to collapse
You must be flashing wrong partition. Or try changing different dd binary e.g. from latest busybox version.
Or if you can loop mount system.img with ext4 filesystem, simple copy files to /system partition along with file permissions.
this time i copied successfully to right partitiones then Wipe DALVIK-CACHE, CACHE & DATA.
then restart but stuck in start loop
sadiq1 said:
this time i copied successfully to right partitiones then Wipe DALVIK-CACHE, CACHE & DATA.
then restart but stuck in start loop
Click to expand...
Click to collapse
Then other firmware partitions from Wiko must be incompatible with QMobile ROM. Simple is to use a flasher which flashes all partitions. But replace the recovery image with custom recovery like TWRP. After that you may flash this rooted ROM if needed.
yar mujhe app se bat kerni he 03343210716/03028484502
I downloaded some firemware for qmobile , using QFile application
every thing was ready when i click on download there was error "download fail:sahara failvalue canot be null"
sadiq1 said:
yar mujhe app se bat kerni he 03343210716/03028484502
Click to expand...
Click to collapse
English please, it's international forum.
PM me for personal assistance.
mirfatif said:
English please, it's international forum.
PM me for personal assistance.
Click to expand...
Click to collapse
He's saying he wants to have a word with you and he has given his number.
x.ak**** said:
He's saying he wants to have a word with you and he has given his number.
Click to expand...
Click to collapse
I know I'm Urdu speaking :laugh:
Just asking to follow the rules.
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