When I tried to unroot my phone, I flashed the wrong firmware and it is now bricked. Since it is bricked I can't check the device/build number in the device settings. I have searched around, and I still have not found a way to truly find the correct firmware for my phone. My phone is a Huawei P10 VTR-L29, but I can't find the rest of the numbers needed to identify the correct firmware.. I've tried to retrieve the device/build number through ADB, but I think I've only been able to recover info from the previous firmware I flashed onto the device. I still have the device's box if that helps.
(By the way, I have considered using FunkyHuawei's services to unbrick my phone, since I am getting very impatient and need to fix my phone ASAP. Please tell me if you have any experience with the company.)
Thank you for reading, please feel free to reply if you have any help/advice, I need all the help I can get.
-August
You should be able to rebrand your phone by flashing a oeminfo file. I can provide you the C432 oeminfo for VTR-L29, this is the international version, should work on every phone.
Otherwise you can try following adb command:
Code:
adb shell getprop | grep ro.product.CustCVersion
But I don't know if this output is correct, when you flashed the wrong firmware.
How did you flash it, btw?
I think you can also use HurUpdater on xda to flash other firmware.
Jannomag said:
You should be able to rebrand your phone by flashing a oeminfo file. I can provide you the C432 oeminfo for VTR-L29, this is the international version, should work on every phone.
Otherwise you can try following adb command:
Code:
adb shell getprop | grep ro.product.CustCVersion
But I don't know if this output is correct, when you flashed the wrong firmware.
How did you flash it, btw?
Click to expand...
Click to collapse
I have tried flashing it multiple ways. I have tried through microSD, ADB sideload, TWRP, etc.
If you could help me with the oeminfo, that would be great.
Is it still possible to do the ADB command even if I can't access sideload?
M1chiel said:
I think you can also use HurUpdater on xda to flash other firmware.
Click to expand...
Click to collapse
Does it work even if I don't have the exactly correct firmware?
AugKri said:
Does it work even if I don't have the exactly correct firmware?
Click to expand...
Click to collapse
You'll have to check that in the HurUpdater thread.
Related
I have an European IS (original sw 1.36.405.1) and i flashed with goldcard to Asian ROM (1.38.707.1). When i tried to reflash EU ROM i get: "Main version older" -this is normal because i flashed a ROM with higher version.
Until we can root the phone there is any possibility to downgrade it? (psneuter+appropriate misc.img?)
same question
but i've got [error 140: incorrect bootloader version]
lge73 said:
I have an European IS (original sw 1.36.405.1) and i flashed with goldcard to Asian ROM (1.38.707.1). When i tried to reflash EU ROM i get: "Main version older" -this is normal because i flashed a ROM with higher version.
Until we can root the phone there is any possibility to downgrade it? (psneuter+appropriate misc.img?)
Click to expand...
Click to collapse
because 1.38.707.1 bootloader is the highest version until now. normally HTC allowed that flash ROM always from low version to higher. so you must waiting for ROOT now. first you'll have to flash BOOTLOADER and RECOVERY, and then you can flash any version ROM.
why not use the goldcard?
Goldcard probably won't work, have to be combined with the misc version change. The misc partition is writeable so downgrading should work. Next few days I'm off so won't make instructions how to do it.
You can try to use the old firmware version number combined with the goldcard. About the same procedure as the DHD or G2 I think.
The name of the zip file should be PB98IMG.zip and has to be on the root of your goldcard.
* not exactly sure about the zip name. Can be found out when booting into bootloader. You get a short flash which file names its looking for.
Ps I'm not responsible for bricks
timbo007up said:
Goldcard probably won't work, have to be combined with the misc version change. The misc partition is writeable so downgrading should work. Next few days I'm off so won't make instructions how to do it.
You can try to use the old firmware version number combined with the goldcard. About the same procedure as the DHD or G2 I think.
The name of the zip file should be PB98IMG.zip and has to be on the root of your goldcard.
* not exactly sure about the zip name. Can be found out when booting into bootloader. You get a short flash which file names its looking for.
Ps I'm not responsible for bricks
Click to expand...
Click to collapse
the name of zip is PG32DIAG.ZIP
timbo007up said:
Goldcard probably won't work, have to be combined with the misc version change. The misc partition is writeable so downgrading should work. Next few days I'm off so won't make instructions how to do it.
You can try to use the old firmware version number combined with the goldcard. About the same procedure as the DHD or G2 I think.
The name of the zip file should be PB98IMG.zip and has to be on the root of your goldcard.
* not exactly sure about the zip name. Can be found out when booting into bootloader. You get a short flash which file names its looking for.
Ps I'm not responsible for bricks
Click to expand...
Click to collapse
Tried to flash via SD card (PG32IMG.zip), don t working.. Main version older!
My question is: if i download misc.img from DHD (or ThunderBolt) and edit with HEX editor (CID number - HTC__32 and sw number for ex:1.35.405.1)and follow the first part of ThunderBolt rooting procedure, i will able to reflash 1.36.405.1 ROM?
Unfortunately I am not familiar with the Android OS, so need some help!
That will probably won't work.
You should take the misc.img from your current rom. But there is also a misc_version script around,you can try that one, I think its in the superoneclick program. Too lazy to search on my phone.
Gl. Again: I'm not responsible for bricks
timbo007up said:
That will probably won't work.
You should take the misc.img from your current rom. But there is also a misc_version script around,you can try that one, I think its in the superoneclick program. Too lazy to search on my phone.
Gl. Again: I'm not responsible for bricks
Click to expand...
Click to collapse
BINGO! Tx timbo007up! With misc_version script i managed to rewrite version number!
So the downgrade was succesfull? Ok than, safe way of downgrading can be ticket off than.
timbo007up said:
So the downgrade was succesfull? Ok than, safe way of downgrading can be ticket off than.
Click to expand...
Click to collapse
Yes it s all right, the downgrade was succesful!
Ok Tnx for testing! Can be of great use later on! I'll notify the rooting team that downgrade is possible.
Lge73 i wrote you a pm...
can you help me ?
You should release ur modded version mate
Sent from my HTC Incredible S using XDA Premium App
also success.
just follow the guide of dhd downgrade(easy to find in dhd forum)
both of RUU and ZIP are ok
tanleiqu said:
also success.
just follow the guide of dhd downgrade(easy to find in dhd forum)
both of RUU and ZIP are ok
Click to expand...
Click to collapse
Yes! You can follow the downgrade procedure:
http://forum.xda-developers.com/showthread.php?t=905003
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
If you got "#" in the result, you have temproot! Proceed:
cd /data/local/tmp/
./misc_version -s 1.35.405.1
Ps I'm not responsible for bricks
Made a guide for it, topic can be closed i suppose.
If u have any further questions do it in de guide topic!
goldcard can only update
zhao, a goldcard is a sdcard that has elevated rights on branded phones, thats the difference so it can also be used for downgrades. its just that the misc_version change is required
can i use these steps to downgrade from gingerbread to froyo?
I've been trying to get my phone up and running but have had no success. I went to sprint and they said since my phone has been tampered and unlocked, they can't do anything except direct me to an XDA post to solve the issue myself. As if I haven't tried that already... So my questions is not about what is wrong with my phone, it is whether anyone knows how to install an OS with the updated 4.06 firmware with the inability to use ADB to push a rom onto my "unable to mount" SDCARD? Sure wish the RUU.exe was out to help...
Any suggestion to flash the firmware: It's been done but unfortunately, it is a partial file. It does not contain the system.img nor is it specified for sprint.
Follow this GUIDE it will get you up and running again
Hi,
I was in the process of flashing new firmware (iI have a thread for this when asking advice and followed the steps on my previous thread) I was flashing firmware 5.11.401.11 which loaded succesfully and rebooted to bootloader.
When it rebooted a driver message cam up I think regarding Qsub or something and the device has frozen or dead.
In the command window it says "wating for device"...i cant seem to get it to do anything!!
My device shows as other devices in my computerQHSUSB-DLOAD and the message I recall was about drivers ...do i need to update them?
Any help please?
Shepps
shepppster said:
Hi,
I was in the process of flashing new firmware (iI have a thread for this when asking advice and followed the steps on my previous thread) I was flashing firmware 5.11.401.11 which loaded succesfully and rebooted to bootloader.
When it rebooted a driver message cam up I think regarding Qsub or something and the device has frozen or dead.
In the command window it says "wating for device"...i cant seem to get it to do anything!!
My device shows as other devices in my computerQHSUSB-DLOAD and the message I recall was about drivers ...do i need to update them?
Any help please?
Shepps
Click to expand...
Click to collapse
Seem's like you may have skipped an important firmware update, which firmware number were you updating from?
If you skipped a firmware version e.g 3.xx.401.x to 5.xx.401.x then you will be needing the Unbrick project here http://forum.xda-developers.com/showthread.php?t=2770684
Danny201281 said:
Seem's like you may have skipped an important firmware update, which firmware number were you updating from?
If you skipped a firmware version e.g 3.xx.401.x to 5.xx.401.x then you will be needing the Unbrick project here http://forum.xda-developers.com/showthread.php?t=2770684
Click to expand...
Click to collapse
I did go consecutively fro 3-4-5 but..I guess It happens. The firmware seemed to flash ok.
I will try the link.
Thanks
shepppster said:
I did go consecutively fro 3-4-5 but..I guess It happens. The firmware seemed to flash ok.
I will try the link.
Thanks
Click to expand...
Click to collapse
Ok the unbricking has worked so far....can someone confirm the fastboot commands in Linux are the same as on a windows CMD prompt please?
I dont want to get this far and not flash the firmware properly.
Danny201281 said:
Seem's like you may have skipped an important firmware update, which firmware number were you updating from?
If you skipped a firmware version e.g 3.xx.401.x to 5.xx.401.x then you will be needing the Unbrick project here http://forum.xda-developers.com/showthread.php?t=2770684
Click to expand...
Click to collapse
Is there a guide on the forum for using Linux so i get the last part (Flashing firmware) perfect please?
shepppster said:
Is there a guide on the forum for using Linux so i get the last part (Flashing firmware) perfect please?
Click to expand...
Click to collapse
Fastboot works just the same in Linux as in Windows with the exception of you must use "sudo"
So
Code:
fastboot devices
becomes
Code:
sudo fastboot devices
Code:
fastboot flash zip firmware.zip
becomes
Code:
sudo fastboot flash zip firmware.zip
and so on if you forget to use sudo you will just see "waiting for device" in which case press ctrl+c to cancel and do command again with sudo :good:
shepppster said:
I did go consecutively fro 3-4-5 but..I guess It happens. The firmware seemed to flash ok.
I will try the link.
Thanks
Click to expand...
Click to collapse
What actually happened is when I was flashing from 4****** to 5***** when I tried to reboot to booloader my PC wanted to reinstall device drivers ,which I think I cancelled by mistake causing the hang up?
I have unbricked and now in bootloader waiting for the device to recharge fully.
I have then got to flash the 5****** series of firmware again(as instructed by the unbrick software).
I will then either install a custom recovery and flash my jellybean back-up or a custom ROM, do you think ARHD 84 will install on the 5***** firmware? I dont fancy going to 6**** until all is ok.
Or is there a way of flashing a stock o/s that can be flashed from TWRP? for the WWE firmware?
Shepps
shepppster said:
What actually happened is when I was flashing from 4****** to 5***** when I tried to reboot to booloader my PC wanted to reinstall device drivers ,which I think I cancelled by mistake causing the hang up?
I have unbricked and now in bootloader waiting for the device to recharge fully.
I have then got to flash the 5****** series of firmware again(as instructed by the unbrick software).
I will then either install a custom recovery and flash my jellybean back-up or a custom ROM, do you think ARHD 84 will install on the 5***** firmware? I dont fancy going to 6**** until all is ok.
Or is there a way of flashing a stock o/s that can be flashed from TWRP? for the WWE firmware?
Shepps
Click to expand...
Click to collapse
Ok I have unbricked my device and used TWRP to recover my back up....however after flashing up to 5******** firmware ,the firmware seems to have reverted back to the 2******* series I started with??? Is that correct?
If so I have to start all over again?
shepppster said:
Ok I have unbricked my device and used TWRP to recover my back up....however after flashing up to 5******** firmware ,the firmware seems to have reverted back to the 2******* series I started with??? Is that correct?
If so I have to start all over again?
Click to expand...
Click to collapse
no firmware does not revert back .. where are you getting these files ?
clsA said:
no firmware does not revert back .. where are you getting these files ?
Click to expand...
Click to collapse
This is the information from my phone the "about" section in settings. software number 2.24.161.1 i havent gone as far as a getvar cmd in fastboot yet,if thats where the correct info will be?
shepppster said:
This is the information from my phone the "about" section in settings. software number 2.24.161.1 i havent gone as far as a getvar cmd in fastboot yet,if thats where the correct info will be?
Click to expand...
Click to collapse
I see in the Unbrick Project Thread your device is fixed But for the record the Software Number in settings is the software number of the rom not the firmware :good: Glad to hear your back up though good job. :highfive:
Danny201281 said:
I see in the Unbrick Project Thread your device is fixed But for the record the Software Number in settings is the software number of the rom not the firmware :good: Glad to hear your back up though good job. :highfive:
Click to expand...
Click to collapse
Ah I thought it might be...all I need know is to move to 6**401 firmware so I can flash the latest ktkt roms (not lolipop) I was a bit of a mare but find it easier to my Ubuntu pc as I dont have to worry about drivers and the like.
Thanks Danny
shepppster said:
Ah I thought it might be...all I need know is to move to 6**401 firmware so I can flash the latest ktkt roms (not lolipop) I was a bit of a mare but find it easier to my Ubuntu pc as I dont have to worry about drivers and the like.
Thanks Danny
Click to expand...
Click to collapse
No Problem, And yeah i'm a Linux user myself and it is the shizzle when it comes to android phones
Danny201281 said:
No Problem, And yeah i'm a Linux user myself and it is the shizzle when it comes to android phones
Click to expand...
Click to collapse
I intend to carry on where I left off...I havent got as far a flashing the new rom.
The 401 firmware I am using is currently 5.11.401.10 ,next step is the 6 series.
Is it best to flash 6.09.401.5 then 401.10,401.11,401.12 consecutively or jump straight to 12?(clearly I dont want to go through the bricking stuff again!!)
Is there a link to a good source of firmware,i looked on the Vomer guide but they are decribed as the dual simHTC one at the download page, is this going to be an issue as I will get them from there as a reliably good source?
http://forum.xda-developers.com/showthread.php?t=2365506
shepppster said:
I intend to carry on where I left off...I havent got as far a flashing the new rom.
The 401 firmware I am using is currently 5.11.401.10 ,next step is the 6 series.
Is it best to flash 6.09.401.5 then 401.10,401.11,401.12 consecutively or jump straight to 12?(clearly I dont want to go through the bricking stuff again!!)
Is there a link to a good source of firmware,i looked on the Vomer guide but they are decribed as the dual simHTC one at the download page, is this going to be an issue as I will get them from there as a reliably good source?
http://forum.xda-developers.com/showthread.php?t=2365506
Click to expand...
Click to collapse
I know that some have jumped strait to the latest without any problems and the theory goes as Lon as you don't skip a version number e.g 3.xx to 5.xx then it should be safe.
Obviously the safest option is to flash each update so you know your not missing anything important. As for a good source I prefer to stick with HTC signed firmware from official OTA updates all of which you can find here http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/
Danny201281 said:
I know that some have jumped strait to the latest without any problems and the theory goes as Lon as you don't skip a version number e.g 3.xx to 5.xx then it should be safe.
Obviously the safest option is to flash each update so you know your not missing anything important. As for a good source I prefer to stick with HTC signed firmware from official OTA updates all of which you can find here http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/
Click to expand...
Click to collapse
@Danny201281 and @clsA Thanks for all your help...successfully flashed up to the latest 6******** firmware and flashed a custom rom.
Perhaps minscule to u guys but massive step forward for me !
Few nailbiting moments anticipating a brick again..but it worked fine using Ubuntu which is much less finicky than windows to use and my weapon of choice from now on!
:good::good:
First of all, what is balong bug?
Balong Bug is when you update to a newer firmware that was not meant for your country, your phone doesn't recognize the correct version of your software(instead of correct version it will show balongc53b311) and you can't do ota update.
So in order to get rid of balong bug, when you update your software to a newer version, in the archive you've downloaded there are 2 folders: one contains the firmware update and one folder named custom or vendor which contains update.app for balong bug.
So all you have to do is to install via local update the update.app from vendor/custom folder.
I've tried to find for as many as possibile versions i could find.
I've made an archive of all vendor folders. Download from here
Here is the list from archive:
B049
B120
B130
B132
B133
B171
B551
Now, in order to get local update back, you'll need to have unlocked bootloader and twrp installed because you'll need to flash an archive.
First, make sure you have installed the correct drivers, then enable usb debugging from developer options(tap 7 times on build number to unlock developer)
To unlock bootloader you'll need to register on huawei then enter your details here.
If you have dual sim,enter your main imei;
After you've done all this you'll have a 10 digit code number, save it.
Now download minimal adb fastboot from here and install it.
Plug the phone into pc, open cmd window in minimal folder(shift + right click -> open new command here), type:
Code:
adb devices
and in return it will show something like
Code:
123213asdsa231 device
. After this type
Code:
adb reboot bootloader
. Now you are in fastboot and here you'll unlock your bootloader by tiping this command:
Code:
fastboot oem unlock yourcode
. If you done all this, now it will show on the bottom Phone Unlocked.
Now you need TWRP from here.
Flash it via fastboot with this command:
Code:
fastboot flash recovery image_name.img
.
Enter twrp, flash this archive.
Now you've got back your local update!.
In order to get back stock recovery, donwload your current firmware version, use huawei extractor to extract recovery.img from update.app and flash it via fastboot with the same command used to flash twrp.
If you have questions, ask here.
Please add the newer B564 to the patch
I'm sorry, but i can't find for b564 ...
hey i tried updating locally on b560, but am stuck at 19% for like half an hour...
Bootloader is now unlocked, fast boot works as i can boot to bootloader but i cant push twrp for some reason.
Edit: fixed, wasn't looking for the correct file to put twrp into.
So i flashed B550 i think which doesn't have Vendor file, how can i get to B551 or one that does, will i need to downgrade first.
BigD18t said:
Bootloader is now unlocked, fast boot works as i can boot to bootloader but i cant push twrp for some reason.
Edit: fixed, wasn't looking for the correct file to put twrp into.
So i flashed B550 i think which doesn't have Vendor file, how can i get to B551 or one that does, will i need to downgrade first.
Click to expand...
Click to collapse
Search for the program that can change your vendor info.
amageek said:
hey i tried updating locally on b560, but am stuck at 19% for like half an hour...
Click to expand...
Click to collapse
What version do you currently running??
VladHD said:
Search for the program that can change your vendor info.
What version do you currently running??
Click to expand...
Click to collapse
I did do that, but it caused my sim to not work at all, not sure what i did after but i now have it all working correctly and no bug.
VladHD said:
Search for the program that can change your vendor info.
What version do you currently running??
Click to expand...
Click to collapse
hey i successfully flashed it... thanks anyways...
P.S. I was on b560 (Poland)...
please reupload archive/files to fix balong bug.
given download link is not working anymore.
huawei2016 said:
please reupload archive/files to fix balong bug.
given download link is not working anymore.
Click to expand...
Click to collapse
Here is the link for vendor information file
https://yadi.sk/d/vxXXNOxss6hjK
Credits: @sokkoban
miststudent2011 said:
Here is the link for vendor information file
https://yadi.sk/d/vxXXNOxss6hjK
Click to expand...
Click to collapse
many thanks dear, many vendors files failed. but your zip file worked well.
now p8 lite dual sim, ale l21 is showing c432b574full update is available. current version is c432b204.
huawei2016 said:
many thanks dear, many vendors files failed. but your zip file worked well.
now p8 lite dual sim, ale l21 is showing c432b574full update is available. current version is c432b204.
Click to expand...
Click to collapse
Good to hear that you solved your problem.
All the credits for the Zip file goes to @sokkoban you should thank him for all his efforts.
My South African ALE-L02 is currently running Android 6.0 C636B530, with the Balong error after the firmware upgrade.. Would I be able to simply flash the Vendor (Custom) file, or do I need to follow other steps first?
hi,
kindly provide the update firmwarefor huawei balong c52b311, and provide solution for locked bootloader to unlock , thanks
Hi im from iran
and my build number is balongc50b311
can I fix it by flashing this file?
menu language is not important for me im using english.
gholamzadeh.mr said:
Hi im from iran
and my build number is balongc50b311
can I fix it by flashing this file?
menu language is not important for me im using english.
Click to expand...
Click to collapse
Yes. Or simply install clean b638 and then personas rom
thank u
i used the app and it worked good.
now my build is c432b132. can i directly flash c432b638 rom?
gholamzadeh.mr said:
thank u
i used the app and it worked good.
now my build is c432b132. can i directly flash c432b638 rom?
Click to expand...
Click to collapse
Not sure but yes try it. First, full wipe everything, than install stock b638 than personas mod.
I did it,
first,I flashed recovery ( it was twrp) and installed stock recovery,
then installed c432b638
my data and apps was not deleted.
@VladHD link is not working
Thanks to ChinHon we have a Dual Sim C432 oeminfo partition backup!
Here it is: https://mega.nz/#F!0pEg0YJL!DOrYXQ8_9nZ5WvZhbBYBgg
This enables dual sim, but most likely you imei will be 000's on the second slot. Now we only need to find a single sim one.
-- Origianl post --
Hi,
In the quest to debrand the single sim version of this phone I could not find any oeminfo dumps. Is there someone with root wiling to dump it?
Thanks!
Edit: You can use the twrp backup function to do it or this application: https://forum.xda-developers.com/android/apps-games/app-partitions-backup-t3003599
i have root on pra-lx1 but i have dual sim, will it be okay for you ?
i don't have twrp...
harlock59 said:
i have root on pra-lx1 but i have dual sim, will it be okay for you ?
i don't have twrp...
Click to expand...
Click to collapse
Yes! It would be great! You can use this program to backup the oeminfo partition https://forum.xda-developers.com/android/apps-games/app-partitions-backup-t3003599 (no twrp required )
Edit: Zip the output file since it is quite large (64mb, but compresses really well)
here's the file https://mon-partage.fr/f/J8GGyO4O/
the file was already zipped by the app !
harlock59 said:
here's the file https://mon-partage.fr/f/J8GGyO4O/
Click to expand...
Click to collapse
Thanks! I will see if I can debrand the phone using this file.
Edit: Apparently your phone is branded to bytel (C530). So I cannot debrand using your backup, still thanks!
i opened the .img with hex edit but i didn't understand what it meant...
---------- Post added at 10:56 PM ---------- Previous post was at 10:55 PM ----------
bytel is Bouygues Telecom, indeed i got it from a carrier
---------- Post added at 10:57 PM ---------- Previous post was at 10:56 PM ----------
why do you want to debrand it ?
---------- Post added at 11:00 PM ---------- Previous post was at 10:57 PM ----------
what if you just remove "bytel/fr" with an hex editor ?
there is also this oem info: 8 - MF B .HXL M x
I have done that with the vodafone one but I still cannot flash a standard rom.
The vodafone firmware doesn't let me change some configs and has a default wifi network that cannot be removed.
I'm on c432b118 using hacks, but some things are not working properly. Still the debranded rom is faster than the vodafone rom, that's the main reason to debrand the phone.
randhackr said:
Hi,
In the quest to debrand the single sim version of this phone I could not find any oeminfo dumps. Is there someone with root wiling to dump it?
Thanks!
Edit: You can use the twrp backup function to do it or this application: https://forum.xda-developers.com/android/apps-games/app-partitions-backup-t3003599
Click to expand...
Click to collapse
I would dump mine but i still have not been able to get my bootloader unlock code
It simply got code to 2 devices at once
randhackr said:
Thanks to ChinHon we have a Dual Sim C432 oeminfo partition backup!
Here it is: https://mega.nz/#F!0pEg0YJL!DOrYXQ8_9nZ5WvZhbBYBgg
This enables dual sim, but most likely you imei will be 000's on the second slot. Now we only need to find a single sim one.
-- Origianl post --
Hi,
In the quest to debrand the single sim version of this phone I could not find any oeminfo dumps. Is there someone with root wiling to dump it?
Thanks!
Edit: You can use the twrp backup function to do it or this application: https://forum.xda-developers.com/android/apps-games/app-partitions-backup-t3003599
Click to expand...
Click to collapse
Your welcome
ts gaming said:
Your welcome
Click to expand...
Click to collapse
What oeminfo is this? C432 single sim? Indeed it is! Thanks After flashing it I no longer have a dual sim phone.
randhackr said:
What oeminfo is this? C432 single sim? Indeed it is! Thanks After flashing it I no longer have a dual sim phone.
Click to expand...
Click to collapse
Can you help me debrand vodafone? All the steps
Nepa1 said:
Can you help me debrand vodafone? All the steps
Click to expand...
Click to collapse
I will give you only a general overview of the process.
First you need an unlocked bootloader, then you need root or a custom recovery.
You will need to use dd to write the oeminfo backup file in to your oeminfo partition. Be very careful with dd, you can easily brick your phone with it.
After that you must unlock the bootloader again (after changing the oeminfo partition it locks again).
After this you will need to flash a stock recovery using fastboot.
The final step is to use firmware finder to flash either B110 for the dual sim version or B115 for the single sim version.
Use dd?
randhackr said:
I will give you only a general overview of the process.
First you need an unlocked bootloader, then you need root or a custom recovery.
You will need to use dd to write the oeminfo backup file in to your oeminfo partition. Be very careful with dd, you can easily brick your phone with it.
After that you must unlock the bootloader again (after changing the oeminfo partition it locks again).
After this you will need to flash a stock recovery using fastboot.
The final step is to use firmware finder to flash either B110 for the dual sim version or B115 for the single sim version.
Click to expand...
Click to collapse
Thank you but this dd what is it?
randhackr said:
I will give you only a general overview of the process.
First you need an unlocked bootloader, then you need root or a custom recovery.
You will need to use dd to write the oeminfo backup file in to your oeminfo partition. Be very careful with dd, you can easily brick your phone with it.
After that you must unlock the bootloader again (after changing the oeminfo partition it locks again).
After this you will need to flash a stock recovery using fastboot.
The final step is to use firmware finder to flash either B110 for the dual sim version or B115 for the single sim version.
Click to expand...
Click to collapse
dd what is it?
Nepa1 said:
dd what is it?
Click to expand...
Click to collapse
dd is a command for copying partition (linux command of course)
Maybe you could search some info before doing this , just to learn more because like randhackr said, it's a dangerous command wich can save you, or kill you (ok not you loooooool but your phone)
ripp2003 said:
dd is a command for copying partition (linux command of course)
Maybe you could search some info before doing this , just to learn more because like randhackr said, it's a dangerous command wich can save you, or kill you (ok not you loooooool but your phone)
Click to expand...
Click to collapse
OK Thank you
randhackr said:
I will give you only a general overview of the process.
First you need an unlocked bootloader, then you need root or a custom recovery.
You will need to use dd to write the oeminfo backup file in to your oeminfo partition. Be very careful with dd, you can easily brick your phone with it.
After that you must unlock the bootloader again (after changing the oeminfo partition it locks again).
After this you will need to flash a stock recovery using fastboot.
The final step is to use firmware finder to flash either B110 for the dual sim version or B115 for the single sim version.
Click to expand...
Click to collapse
Done unlocking bootloader process
Installed twrp backup oeminfo vodafone saved on pc then changed
Oeminfo no brand and did oeminfo restore with twrp after with fastboot flash firmware b115 but nn start
English excuse
randhackr said:
I will give you only a general overview of the process.
First you need an unlocked bootloader, then you need root or a custom recovery.
You will need to use dd to write the oeminfo backup file in to your oeminfo partition. Be very careful with dd, you can easily brick your phone with it.
After that you must unlock the bootloader again (after changing the oeminfo partition it locks again).
After this you will need to flash a stock recovery using fastboot.
The final step is to use firmware finder to flash either B110 for the dual sim version or B115 for the single sim version.
Click to expand...
Click to collapse
How do I get a stock recovery image? And how do I use firmware finder? (please detail)
Thanks in advance.