Related
Just share the ROM using now, for those who want to keep BL locked.
Please note that this is a Japan version, for WiFi models.
STOCK 10.1.C.0.370 JP
Recovery Pre-installed
Pre-Rooted
Reboot issue Fixed (Credit goes to @Carceri, Modified a bit to make it work. Another solution by @[NUT] :[Locked Bootloader] The definitive root Remount-Reboot fix!)
Init.d support
Nothing more～
Download Here：
Part1 Part2
Installation:
1. Backup everything in case of any bad luck.
2a. Flash 370 FTF without system and data.
2b.1. Or update to 370 official with SONY Update Service for more insurance (This will WIPE EVERYTHING if 370 already installed/it failed to update, Confirm your Backup 65535 times before start).
2b.2. Unplug and Flash 344 FTF, system only.
3. Get root with Bin4ry's tool.
4. Install Recovery.
5. Flash the zip.
does bootloader need to be unlocked for this?
shaun.s said:
does bootloader need to be unlocked for this?
Click to expand...
Click to collapse
No，it's for locked BL so recovery and root/su are integrated, which can be provided by a custom kernel.
Fishmanzero said:
No，it's for locked BL so recovery and root/su are integrated, which can be provided by a custom kernel.
Click to expand...
Click to collapse
you rock!
thanks downloading now
---------- Post added at 06:20 PM ---------- Previous post was at 06:17 PM ----------
Fishmanzero said:
No，it's for locked BL so recovery and root/su are integrated, which can be provided by a custom kernel.
Click to expand...
Click to collapse
is this for 16GB version?
I have 32GB LTE
shaun.s said:
you rock!
thanks downloading now
---------- Post added at 06:20 PM ---------- Previous post was at 06:17 PM ----------
is this for 16GB version?
I have 32GB LTE
Click to expand...
Click to collapse
Internal storage size doesn't matter in this case I think, but 10.1.C.0.370 is for WiFi model and LTE model's firmwares use a different build, like 10.1.E.0.265.
It is not recommended to flash a different zip...
If you are already up to date and only want root, reboot fix or recovery, try @DooMLoRD's new root tool and the fix mentioned in the #1.
Fishmanzero said:
Internal storage size doesn't matter in this case I think, but 10.1.C.0.370 is for WiFi model and LTE model's firmwares use a different build, like 10.1.E.0.265.
It is not recommended to flash a different zip...
If you are already up to date and only want root, reboot fix or recovery, try @DooMLoRD's new root tool and the fix mentioned in the #1.
Click to expand...
Click to collapse
Hi Fisherman, your links are down, could you please check it? or maybe create a mirror on another server?
By the way, is this a FTF file? or flasheable ZIP? i guess is a FTF because i read on DoomLord thread that in order to flash recovery you need to have the bootloader unlocked.
Thank you.
juanyunis said:
Hi Fisherman, your links are down, could you please check it? or maybe create a mirror on another server?
By the way, is this a FTF file? or flasheable ZIP? i guess is a FTF because i read on DoomLord thread that in order to flash recovery you need to have the bootloader unlocked.
Thank you.
Click to expand...
Click to collapse
d-h.st seems down now...
Cannot upload at the moment, if d-h.st does not recovers tomorrow I will upload to another mirror.
And this is a CWM flashable zip as stated in the title.
Also installing recovery does not necessarily require unlocked BL/Custom Kernel, it can be installed on a rooted rom. Find a version works in that way~
A working one attached:
Fishmanzero said:
d-h.st seems down now...
Cannot upload at the moment, if d-h.st does not recovers tomorrow I will upload to another mirror.
And this is a CWM flashable zip as stated in the title.
Also installing recovery does not necessarily require unlocked BL/Custom Kernel, it can be installed on a rooted rom. Find a version works in that way~
A working one attached:
Click to expand...
Click to collapse
Oh nice. I guess he stated that before because the system rw reboot issue, so the best way to achieve that was using fastboot. Thank you man!
I don't understand some points in the installation instructions.
1) Why must the 370 FTF / update be flashed first? When anyway after that 344 must be flashed???
2) When the bootloader is unlocked, I can install / run CWM directly and flash this ROM here directly, or can't I??
hasenbein1966 said:
I don't understand some points in the installation instructions.
1) Why must the 370 FTF / update be flashed first? When anyway after that 344 must be flashed???
2) When the bootloader is unlocked, I can install / run CWM directly and flash this ROM here directly, or can't I??
Click to expand...
Click to collapse
Well in the instructions he said:
1. the .370 without flashing system.sin and userdata.sin, that means, only stuff not related to the system partition and well, you can keep your data because userdata.sin is not selected.
2. the .344 only system.sin because this is the one with most opportunities to root using bin4ry tool.
3. then in the files he provides, you will have the 370 system with all the fixes but that one is a CWM flash file, so you will need to install the recovery and then flash this file. See the attachment he posted here.
If your bootloader is unlocked you can use fastboot to flash the recovery. Also you can skip flashing those FTF files, and just flash the CWM file. But i believe that someone confirmed that you won't need this because if your bootloader is unlocked you can install root and remount /system without any issues.
---------- Post added at 06:58 AM ---------- Previous post was at 06:52 AM ----------
Fishmanzero said:
d-h.st seems down now...
Cannot upload at the moment, if d-h.st does not recovers tomorrow I will upload to another mirror.
And this is a CWM flashable zip as stated in the title.
Also installing recovery does not necessarily require unlocked BL/Custom Kernel, it can be installed on a rooted rom. Find a version works in that way~
A working one attached:
Click to expand...
Click to collapse
I had to adapt the script because i'm running Mac OSX 10.8.4. but this worked perfect, i've CWM recovery with a locked bootloader, only problem is that it can mount my microsd card, maybe is missing the exfat module.
Thank you!
juanyunis said:
I had to adapt the script because i'm running Mac OSX 10.8.4. but this worked perfect, i've CWM recovery with a locked bootloader, only problem is that it can mount my microsd card, maybe is missing the exfat module.
Thank you!
Click to expand...
Click to collapse
Yes this CWMR does not have exFAT support, and this ROM includes the same one.
Fishmanzero said:
Yes this CWMR does not have exFAT support, and this ROM includes the same one.
Click to expand...
Click to collapse
So great yeah :laugh:
this means i can root+get recovery on .370 with locked bootloader if i get i right ?
i have a sgp 311 wifi on official 370 installed - wil this work then ??
Greetz
-----------------------
If anyone need a mirror let me know !!
-----------------------
How do i flash in flash tool it dosent reconigze image when put in firmwares?????
spoonymoon said:
So great yeah :laugh:
this means i can root+get recovery on .370 with locked bootloader if i get i right ?
i have a sgp 311 wifi on official 370 installed - wil this work then ??
Greetz
-----------------------
If anyone need a mirror let me know !!
-----------------------
Click to expand...
Click to collapse
Since you have already updated firmware, no need to install this if the new rootkits work, try them.
Find DooMLoRD's above.
Translated Japanese toolkit from 2ch in attachment.
If they don't apply to our Tablet Z, you will have to flash 344 FTF (system only) then do the rest.
Fishmanzero said:
Since you have already updated firmware, no need to install this if the new rootkits work, try them.
Find DooMLoRD's above.
Translated Japanese toolkit from 2ch in attachment.
If they don't apply to our Tablet Z, you will have to flash 344 FTF (system only) then do the rest.
Click to expand...
Click to collapse
thanx
your attched files does say it installs root ok - but when checked after reboot - no root ?
but why not flash 370. pre rooted insted? and not least HOW do i flash it? its not a ftf file
spoonymoon said:
thanx
your attched files does say it installs root ok - but when checked after reboot - no root ?
but why not flash 370. pre rooted insted? and not least HOW do i flash it? its not a ftf file
Click to expand...
Click to collapse
You can not flash a CWM zip without recovery, and it need root to install one, and no root for 370 now
So it's necessary to download a 344 FTF, flash the system part only, and use the old working toolkit to root it.
It may be very likely to fail on different devices because the rootkit uses a kernel exploit, the address for which to run just usually varies from kernel to kernel.
Wait for our great devs to figure out the working address will be the most painless.
Or do the operations in the OP, and of course install a custom kernel after unlocking BL if you don't mind doing so, is way faster atm.
Here's an older rootkit also from 2ch. Try it if interested.
Fishmanzero said:
You can not flash a CWM zip without recovery, and it need root to install one, and no root for 370 now
So it's necessary to download a 344 FTF, flash the system part only, and use the old working toolkit to root it.
It may be very likely to fail on different devices because the rootkit uses a kernel exploit, the address for which to run just usually varies from kernel to kernel.
Wait for our great devs to figure out the working address will be the most painless.
Or do the operations in the OP, and of course install a custom kernel after unlocking BL if you don't mind doing so, is way faster atm.
Here's an older rootkit also from 2ch. Try it if interested.
Click to expand...
Click to collapse
Thanx a lot
tried and same result, says its rooted and its not - but you´re right better wait a bit for better solution , that dosent involve any risk !!
(wife and kid is going to ´kill´me if it f... up soo )
spoonymoon said:
Thanx a lot
tried and same result, says its rooted and its not - but you´re right better wait a bit for better solution , that dosent involve any risk !!
(wife and kid is going to ´kill´me if it f... up soo )
Click to expand...
Click to collapse
And yes, Japanese user got it work:laugh:
370
Fishmanzero said:
And yes, Japanese user got it work:laugh:
370
Click to expand...
Click to collapse
Woooow it f..... works i´ve got root .....wiiiiii :laugh::good::good::good::good::good::good::good::good:
i ow you big time
thanx thanx
is their a possibility for SGP321 with 10.1.1.A.1.307 too?
Fishmanzero said:
Reboot issue Fixed (Credit goes to @Carceri, Modified a bit to make it work. New solution also from him: [Locked Bootloader] The definitive root Remount-Reboot fix!)
Click to expand...
Click to collapse
Heh, you are pointing to a thread by me but refer to a fix done by Carceri ... who's are you using exactly?
I know that there are some threads over this topic, but there is nowhere a specific answer. I have currently Sokkoban's ROM, and I want to revert to the official build. Can someon provide me with the necessary files in order to flash a stock recovery? I found only this answer, but there are no available links for the files. I would appreciate if anyone could help me. I have ALE L21- dual european edition, running on custom rom based on C432B574.
Thanks in advance.
Edit: tried with the HuaweiUpdateExtractor with the UPDATE.APP file, and flashed the first 3 images (boot, recovery cust) but I get an error while trying to flash the system.img.
http://www.carbontesla.com/2016/07/download-huawei-p8-lite-b574-full-marshmallow-firmware-europe/ download this, put dload folder on sd card, and flash with 3 buttons method
speedster_no1 said:
http://www.carbontesla.com/2016/07/download-huawei-p8-lite-b574-full-marshmallow-firmware-europe/ download this, put dload folder on sd card, and flash with 3 buttons method
Click to expand...
Click to collapse
Thanks. I am gonna try it tomorrow. I 've been trying all day to find a way. I hope this will work!
Edit : it didn't work. Thanks anyway.
spirto82 said:
Thanks. I am gonna try it tomorrow. I 've been trying all day to find a way. I hope this will work!
Edit : it didn't work. Thanks anyway.
Click to expand...
Click to collapse
Sokkoban too said to flash 4 images, but i too got error while flashing system image...
Sent from my ALE-L21 using XDA-Developers mobile app
amageek said:
Sokkoban too said to flash 4 images, but i too got error while flashing system image...
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
It got messy after installing the 4 images. I tried this post and got myself with B052 and emui 4.0. Later I tried our post MEGA-THREAD ALE-L21, ALE-L23, ALE-L02, Converting, Root, Unbrick, Updating, Xposed - chapter 4: Unbricking but nothing.
spirto82 said:
It got messy after installing the 4 images. I tried this post and got myself with B052 and emui 4.0. Later I tried our post MEGA-THREAD ALE-L21, ALE-L23, ALE-L02, Converting, Root, Unbrick, Updating, Xposed - chapter 4: Unbricking but nothing.
Click to expand...
Click to collapse
Well for now, i am happy with sokkoban's deodexed rom..
Got light painting, removed bloatware, xposed compatible... So no complains.. I just wanted to make sure that going back is possible, and some say it is by flashing 4 images... But not with us.. Anyways will keep you updated if i find something new...
amageek said:
Well for now, i am happy with sokkoban's deodexed rom..
Got light painting, removed bloatware, xposed compatible... So no complains.. I just wanted to make sure that going back is possible, and some say it is by flashing 4 images... But not with us.. Anyways will keep you updated if i find something new...
Click to expand...
Click to collapse
You are absolutely right. Although Sokkoban's ROM is really very good, you cannot go back to the official easily. Still din't try to flash another rom, like cm 11 and then go back to the official. If anyones does try it, he should let us know.
spirto82 said:
I know that there are some threads over this topic, but there is nowhere a specific answer. I have currently Sokkoban's ROM, and I want to revert to the official build. Can someon provide me with the necessary files in order to flash a stock recovery? I found only this answer, but there are no available links for the files. I would appreciate if anyone could help me. I have ALE L21- dual european edition, running on custom rom based on C432B574.
Thanks in advance.
Edit: tried with the HuaweiUpdateExtractor with the UPDATE.APP file, and flashed the first 3 images (boot, recovery cust) but I get an error while trying to flash the system.img.
Click to expand...
Click to collapse
You need to flash the original recovery(which you already have). Then put dload folder in sdcard and upgrade manually. You might get BALONG bug (because this happened to me) so I recommend you to start from beginning( the very first firmware for your model/country). For me it was B120. It contained two dload folders one was the system and the other was vendor file. You need both files.
Suleiman01 said:
You need to flash the original recovery(which you already have). Then put dload folder in sdcard and upgrade manually. You might get BALONG bug (because this happened to me) so I recommend you to start from beginning( the very first firmware for your model/country). For me it was B120. It contained two dload folders one was the system and the other was vendor file. You need both files.
Click to expand...
Click to collapse
Tried everything. Even the files for converting into dual. The only thing I managed to get, was: Sokkoban's ROM, and after a factory reset, I got B052 with EMUI 4. Hopefully someone will find a way and create a guide.
spirto82 said:
Tried everything. Even the files for converting into dual. The only thing I managed to get, was: Sokkoban's ROM, and after a factory reset, I got B052 with EMUI 4. Hopefully someone will find a way and create a guide.
Click to expand...
Click to collapse
I reverted back using the same procedure. What do you mean by converting files to dual? Isn't your phone already dual sim?
---------- Post added at 05:34 PM ---------- Previous post was at 05:27 PM ----------
Suleiman01 said:
I reverted back using the same procedure. What do you mean by converting files to dual? Isn't your phone already dual sim?
Click to expand...
Click to collapse
If you are on B052 (official) and did not have balong bug then I think you can update to emui 4.0/Android 6.0 without any issues.
Suleiman01 said:
I reverted back using the same procedure. What do you mean by converting files to dual? Isn't your phone already dual sim?
If you are on B052 (official) and did not have balong bug then I think you can update to emui 4.0/Android 6.0 without any issues.
Click to expand...
Click to collapse
I used MEGA-THREAD ALE-L21, ALE-L23, ALE-L02, Converting, Root, Unbrick, Updating, Xposed - chapter 4: Unbricking but didn't work. Then I tried to revert to B052, but as I wrote before, I had Sokkoban's ROM and after a factory reset, I had B052 with emui 4.0 installed. If you know a working procedure to return to the official build, I suggest you write a guide.
spirto82 said:
I used MEGA-THREAD ALE-L21, ALE-L23, ALE-L02, Converting, Root, Unbrick, Updating, Xposed - chapter 4: Unbricking but didn't work. Then I tried to revert to B052, but as I wrote before, I had Sokkoban's ROM and after a factory reset, I had B052 with emui 4.0 installed. If you know a working procedure to return to the official build, I suggest you write a guide.
Click to expand...
Click to collapse
By the way do you have nandroid backup of official rom? If yes restore it via twrp. This could save you a lot of time. The method I used isn't difficult but it takes time.
On sokoban's rom. Flash the original recovery (recommend that you extract it from the firmware you are going to flash).Use the oldest one (link given below) emui 3.1/Android 5.0 for dual sim
Now put dload file in sdcard/internal memory and upgrade the phone.
If you have balong bug put dload2(rename it to dload) folder in sdcard/ internal memory and upgrade.
Now later you may upgrade to Android 6.0/emui 4
Link for firmware Europe
https://goo.gl/KQ0b6L
Suleiman01 said:
By the way do you have nandroid backup of official rom? If yes restore it via twrp. This could save you a lot of time. The method I used isn't difficult but it takes time.
On sokoban's rom. Flash the original recovery (recommend that you extract it from the firmware you are going to flash).Use the oldest one (link given below) emui 3.1/Android 5.0 for dual sim
Now put dload file in sdcard/internal memory and upgrade the phone.
If you have balong bug put dload2(rename it to dload) folder in sdcard/ internal memory and upgrade.
Now later you may upgrade to Android 6.0/emui 4
Link for firmware Europe
https://goo.gl/KQ0b6L
Click to expand...
Click to collapse
No, I used TWRP backup.
When I tried to extract the images from an official ROM (I have done so many attempts that, I cannot remember which ROM I used), I was able to flash 3 out 4 files. The one I couldn't was the system. When I tried through classic (dload etc), It got stuck at 2% and would give me an error.
But that's all in the past. lol
At this moment, my phone is at the service center with no warranty cause my wifi adapter is not working. From what I've heard, such ptoblems, need mainboard replacement and I cannot afford it at this moment. So I am going to stuck with this phone till it's dead, and of course not going to install any ROM, just because I cannot update anything..... cheers!!!
spirto82 said:
I know that there are some threads over this topic, but there is nowhere a specific answer. I have currently Sokkoban's ROM, and I want to revert to the official build. Can someon provide me with the necessary files in order to flash a stock recovery? I found only this answer, but there are no available links for the files. I would appreciate if anyone could help me. I have ALE L21- dual european edition, running on custom rom based on C432B574.
Thanks in advance.
Edit: tried with the HuaweiUpdateExtractor with the UPDATE.APP file, and flashed the first 3 images (boot, recovery cust) but I get an error while trying to flash the system.img.
Click to expand...
Click to collapse
Well tbh, you can simply convert the system.img using simg2img.exe and then make a flashable zip.
then you can install the system.img withing recovery
Hey guys,
I am trying to intall a custom rom on my blu vivo xl. My worries are that i either soft-brick the phone or boot the new rom and having no signal due to no imei, or no 4G due to band change if it's even possible. I'll leave you with some reliable data:
-arch64 procesor
-5.1 stock android : BLU_V0030UU_V07_GENERIC 25-01-2016
- 3.10.65+ kernel
- Rooted with kingoroot
- Previously had xposed, but uninstalled due to random reboots.
I was looking to install aospextended rom:
https://forum.xda-developers.com/vivo-xl/development/rom-aospextended-rom-v4-1-t3592932
I'd really appreciate if you could orient me or refer me to a post with instructions, since i didn't find one. It's been some years since i don't do this back to the legendary HTC HD2 and i'm missing it btw
Thanks!
Nacho
https://forum.xda-developers.com/vivo-xl/how-to/fix-soft-brickedcannot-enter-recovery-t3594733
Unfortunately most custom ROMs in this forum were based off Gionee so likely you will get no SIM. Use your stock ROM /etc/firmware folder to replace that in ROM.
min1968 said:
https://forum.xda-developers.com/vivo-xl/how-to/fix-soft-brickedcannot-enter-recovery-t3594733
Unfortunately most custom ROMs in this forum were based off Gionee so likely you will get no SIM. Use your stock ROM /etc/firmware folder to replace that in ROM.
Click to expand...
Click to collapse
Thank you for your response.
I've already got twrp installed for 5.1
So i should just install this MM based ROM i said on the post and replace /etc/firmware folder?
Or i need to install stock MM from ota first?
Thing is, i cant OTA update, it says that the system is corrupted, i even tried from twrp but no luck
I've seen that i need stock mm to be able to install most of the custom rom's in xda
Thing is i can't install any OTA update. Should i flash 5.1 stock rom on top of the modified one i'm running?
By modified i am talking about the root and xposed, which is the cause i cant OTA
Nacholer said:
I've seen that i need stock mm to be able to install most of the custom rom's in xda
Thing is i can't install any OTA update. Should i flash 5.1 stock rom on top of the modified one i'm running?
By modified i am talking about the root and xposed, which is the cause i cant OTA
Click to expand...
Click to collapse
Follow my steps exactly then you can do OTA to MM.
The key is to use the 8 files backup to restore stock 5.1, not the backup only includes 4 files.
min1968 said:
Follow my steps exactly then you can do OTA to MM.
The key is to use the 8 files backup to restore stock 5.1, not the backup only includes 4 files.
Click to expand...
Click to collapse
Alright, ill do that. Tried with the 4 files backup last night, didn't work as you just told.
Do you have a link to the 5.1 stock recovery i should flash with sp flash tool? I can't find it anywhere. It wont work if i still have twrp installed, right?
Thanks! i really appreciate it, and great guide btw
min1968 said:
Follow my steps exactly then you can do OTA to MM.
The key is to use the 8 files backup to restore stock 5.1, not the backup only includes 4 files.
Click to expand...
Click to collapse
I installed the 11 files backup and i still can't get ota. I should install the stock recovery, right? got a link for that?
Thank you in advance!
In my case I have a fully working STOCK but ROOTED Marshmallow Blu Vivo XL with working IMEI, but as soon as I wipe and install say AEX rom, I lose both IMEI functions and also get the dreaded wifi NVRAM error (but working wifi).
I also restored the etc/firmware directory to AEX but it wont help regain IMEI functionality.
MTK Engineering mode does not work on AEX because it complains not being stock rom so it closes.
For the life of me, I can't make a connection to the PC through SP Flash Tool too.
Any pointers?
TIA!
Nacholer said:
I installed the 11 files backup and i still can't get ota. I should install the stock recovery, right? got a link for that?
Thank you in advance!
Click to expand...
Click to collapse
Yes need stock recovery to do OTA.
https://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
---------- Post added at 03:00 PM ---------- Previous post was at 02:56 PM ----------
Rayan said:
In my case I have a fully working STOCK but ROOTED Marshmallow Blu Vivo XL with working IMEI, but as soon as I wipe and install say AEX rom, I lose both IMEI functions and also get the dreaded wifi NVRAM error (but working wifi).
I also restored the etc/firmware directory to AEX but it wont help regain IMEI functionality.
MTK Engineering mode does not work on AEX because it complains not being stock rom so it closes.
For the life of me, I can't make a connection to the PC through SP Flash Tool too.
Any pointers?
TIA!
Click to expand...
Click to collapse
Read above my #2 post on customer ROMs in this forum.
And my this post to rescue your Blu Vivo XL :
https://forum.xda-developers.com/vivo-xl/how-to/fix-soft-brickedcannot-enter-recovery-t3594733
min1968 said:
Yes need stock recovery to do OTA.
https://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
Thank you!! i'll try that and report back.
Click to expand...
Click to collapse
min1968 said:
Yes need stock recovery to do OTA.
https://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
---------- Post added at 03:00 PM ---------- Previous post was at 02:56 PM ----------
Read above my #2 post on customer ROMs in this forum.
And my this post to rescue your Blu Vivo XL :
https://forum.xda-developers.com/vivo-xl/how-to/fix-soft-brickedcannot-enter-recovery-t3594733
Click to expand...
Click to collapse
Thanks for the reply Min1968!
Yes, I know how to recover IMEI on the stock ROM and I'm currently running stock MM rooted with working IMEI.
The problem I have is that I can't run custom ROMs even if I try the etc/firmware trick you mentioned.
What is the stock TWRP partition that has the modem and IMEI? Maybe if I flash it back through TWRP once I get AEX rom up and running?
Thanks!
min1968 said:
Yes need stock recovery to do OTA.
https://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
---------- Post added at 03:00 PM ---------- Previous post was at 02:56 PM ----------
Click to expand...
Click to collapse
Hey, i got into deep trouble. i Factory reseted the phone. Then did fastboot oem unlock, flashed by fastboot flash recovery, the stock recovery img. After that, the phone boot-loops. I installed back twrp and it sais : Unable to mount /data
Now i can't access my internal memory and i'm stuck. Please help me!
Thanks, i really appreciate this
Nacholer said:
Hey, i got into deep trouble. i Factory reseted the phone. Then did fastboot oem unlock, flashed by fastboot flash recovery, the stock recovery img. After that, the phone boot-loops. I installed back twrp and it sais : Unable to mount /data
Now i can't access my internal memory and i'm stuck. Please help me!
Thanks, i really appreciate this
Click to expand...
Click to collapse
Okay, i fixed it reformatting the data partition on twrp. Thing is, when i want to install the recovery that happens. Maybe if i dont oem unlock?
well, i did that and it booted with the stock recovery. But i still can't OTA, i really dont know why, i even could not when i bought the phone
Nacholer said:
Hey guys,
I am trying to intall a custom rom on my blu vivo xl. My worries are that i either soft-brick the phone or boot the new rom and having no signal due to no imei, or no 4G due to band change if it's even possible. I'll leave you with some reliable data:
-arch64 procesor
-5.1 stock android : BLU_V0030UU_V07_GENERIC 25-01-2016
- 3.10.65+ kernel
- Rooted with kingoroot
- Previously had xposed, but uninstalled due to random reboots.
I was looking to install aospextended rom:
https://forum.xda-developers.com/vivo-xl/development/rom-aospextended-rom-v4-1-t3592932
I'd really appreciate if you could orient me or refer me to a post with instructions, since i didn't find one. It's been some years since i don't do this back to the legendary HTC HD2 and i'm missing it btw
Thanks!
Nacho
Click to expand...
Click to collapse
to get imei working https://forum.xda-developers.com/vivo-xl/help/solution-to-sim-detected-flashing-t3620224
hi guys i have a friend who had tried to root the huawei p8 lite 2017 with this guide,https://newesc.com/root-al-huawei-p8-lite-2017/ , he have this version of the firmware pra-lx1c55b105 after the flash of this kernel for the root , the phone is gone to a bootloop so my friend it's entered to the recovery and than wiped all and the phone works again , the phone had the root but he have a lot of problem if i go to the developer mode and try to open it comes a blank page and than he retun to the setting the same thing appear when i try to open the setting to enable the unkown source for the app, and the last problem is who he can't uninstall the app after installed , the only way to unistall is with titanium backup but the phone force reboot when it uninstall it .... so anyone had this problem? how i need to solve ? i really need a help for him , sorry for my bad english but i'm italian
halfboss said:
hi guys i have a friend who had tried to root the huawei p8 lite 2017 with this guide,https://newesc.com/root-al-huawei-p8-lite-2017/ , he have this version of the firmware pra-lx1c55b105 after the flash of this kernel for the root , the phone is gone to a bootloop so my friend it's entered to the recovery and than wiped all and the phone works again , the phone had the root but he have a lot of problem if i go to the developer mode and try to open it comes a blank page and than he retun to the setting the same thing appear when i try to open the setting to enable the unkown source for the app, and the last problem is who he can't uninstall the app after installed , the only way to unistall is with titanium backup but the phone force reboot when it uninstall it .... so anyone had this problem? how i need to solve ? i really need a help for him , sorry for my bad english but i'm italian
Click to expand...
Click to collapse
IDEM!! COMPLETELY IDEM! I had the pra-lx1c55b105 too, and, after root, I have your same problems too! Please, someone help us!!!
nobody read the multiple thread about this problem ?
Sorry but it's really annoying. (it's not about you, nothing personnal
Your problem is related to a different version between the boot_root image and, the system partition...
You could try to update your phone to the latest firmware (so you have to configure the wifi and then check in the "about" page for an update)
If an update if available, then I think this will solve your problem.
And be very carefull, never install (apk or worse, flash a partition ) something if no version is specified
My friend had maked the update over Wi-Fi but after the download the flash in the recovery fails, why ? @ripp2003 can you link me where la located this theard ? Thanks a lot
halfboss said:
My friend had maked the update over Wi-Fi but after the download the flash in the recovery fails, why ? @ripp2003 can you link me where la located this theard ? Thanks a lot
Click to expand...
Click to collapse
https://forum.xda-developers.com/p8lite/p8-lite-2017-discussion/how-to-root-huawei-p8-lite-2017-android-t3582179
But this topic is related to PR1-LX1C432B110 and this is the source of newesc.... (this topic got a lot of informations on how to find your firmware)
So right now, you need the exact version of the firmware : I think it's pra-lx1c55b105
-> Find it and download it with Huawei Firmware Finder
-> Extract the boot.img from the firmware with Huawei Firmware Extractor (or maybe you've done a copy before flash the boot_root.img ?)
-> fastboot flash boot boot.img
You 'll lost root but this way, I think you can recover your phone
If this doesnt work, I'm really sorry but, you have to wait for some developpers to make Rom....or, some special things for recover an official firmware.
I'm sorry, this situation is a bullsh**
Really Good luck
@ripp2003 thanks a lot, i had tell this to my friend and Now He try
@ripp2003 bad news after the flash of the kernel rom the Phone is soft bricked , it appears the tim logo than reboot in recovery , He has tried to flash the full rom from the recovery but only install failed
halfboss said:
@ripp2003 bad news after the flash of the kernel rom the Phone is soft bricked , it appears the tim logo than reboot in recovery , He has tried to flash the full rom from the recovery but only install failed
Click to expand...
Click to collapse
Even after doing a full wipe whith manual calling recovery ?
ripp2003 said:
nobody read the multiple thread about this problem ?
Sorry but it's really annoying. (it's not about you, nothing personnal
Your problem is related to a different version between the boot_root image and, the system partition...
You could try to update your phone to the latest firmware (so you have to configure the wifi and then check in the "about" page for an update)
If an update if available, then I think this will solve your problem.
And be very carefull, never install (apk or worse, flash a partition ) something if no version is specified
Click to expand...
Click to collapse
ripp2003 said:
Even after doing a full wipe whith manual calling recovery ?
Click to expand...
Click to collapse
Manual calling recovery?
Recovery: Vol. + and power without PC connection
Then you can make a full wipe, try this
ripp2003 said:
https://forum.xda-developers.com/p8lite/p8-lite-2017-discussion/how-to-root-huawei-p8-lite-2017-android-t3582179
But this topic is related to PR1-LX1C432B110 and this is the source of newesc.... (this topic got a lot of informations on how to find your firmware)
So right now, you need the exact version of the firmware : I think it's pra-lx1c55b105
-> Find it and download it with Huawei Firmware Finder
-> Extract the boot.img from the firmware with Huawei Firmware Extractor (or maybe you've done a copy before flash the boot_root.img ?)
-> fastboot flash boot boot.img
You 'll lost root but this way, I think you can recover your phone
If this doesnt work, I'm really sorry but, you have to wait for some developpers to make Rom....or, some special things for recover an official firmware.
I'm sorry, this situation is a bullsh**
Really Good luck
Click to expand...
Click to collapse
The problem is to find it... On the internet I can't find anything, and on firmware finder too. I need the stock PRA-LX1C55B105 firmware (especially the boot.img) but the problem is to find it. I can't find it anywhere!!!
Please help
I Think what firmware finder isn't really good, someone know another method to download firmware or part of firmware like the boot.img?
halfboss said:
I Think what firmware finder isn't really good, someone know another method to download firmware or part of firmware like the boot.img?
Click to expand...
Click to collapse
I think it's this one, the Prague-L11C55B105
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1458/g104/v75035/f1/full/update.zip
ripp2003 said:
I think it's this one, the Prague-L11C55B105
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1458/g104/v75035/f1/full/update.zip
Click to expand...
Click to collapse
I'm not enough brave to risk the death of my device... Are you sure this is good for my device?
Manuele1000 said:
I'm not enough brave to risk the death of my device... Are you sure this is good for my device?
Click to expand...
Click to collapse
If your phone is softbrick, you could try but, I can't tell you this will work at 100%
With this new phone, we actually try a lot of things to see what happened and..... we are now all beta testers lol
I'm sorry but I can't promise you anything : this si what I've found with Huawei firmare finder so source is OK but like I sait : the version is Prague-L11C55B105 and the firmware is full OTA
My is pra-lx1c55b105
I have the same problem as Napoli.
I will try the Prague-L11C55B105 and I will let you know what hapend...
krousnik said:
My is pra-lx1c55b105
I have the same problem as Napoli.
I will try the Prague-L11C55B105 and I will let you know what hapend...
Click to expand...
Click to collapse
Yeah, thank you!! Let me know if you can boot the phone with that stock kernel, and if security and developper options works. Try the Webcam and the music player too, thank you!
Manuele1000 said:
Yeah, thank you!! Let me know if you can boot the phone with that stock kernel, and if security and developper options works. Try the Webcam and the music player too, thank you!
Click to expand...
Click to collapse
OMG!!! It worked! The phone booted with the stock kernel.
---------- Post added at 02:18 AM ---------- Previous post was at 02:14 AM ----------
Music player is working, camera also working... its back on pra-lx1c55b105.
krousnik said:
OMG!!! It worked! The phone booted with the stock kernel.
---------- Post added at 02:18 AM ---------- Previous post was at 02:14 AM ----------
Music player is working, camera also working... its back on pra-lx1c55b105.
Click to expand...
Click to collapse
Oh my God yeah!! Today afternoon I will try it! So, works everything? Security and developper options too? Yeah bro, very thank you!!
-------------------------------------
Can you tell me what you did? You flashed the entire zip, or only the boot.img? And how? With twrp right?
Yes everything works. I did factory reset and the phone is back to default.
I extracted BOOT image and RECOVERY image with HuaweiUpdateExtractor.
After that with I copied both BOOT and RECOVERY image in Minimal ADB and Fastboot folder.
At last I've connected the phone to PC and flashed BOOT and RECOVERY image.
I've disconnected the phone booted in recovery did factory reset and after that phone booted normally.
Hi all!
First a warning: I tell you how what I done, applying this on different model is possible but require some knowledge... don't try if you are not enough experienced.
My BTV-DL09 had a C100B303 firmware (unlocked, rooted with SuperSu 2.82) and I wanted to upgrade to last version, B310, downloaded with Firmware Finder for Huawei.
But this formware is not yet approved for my device! So i searched a way to update the firmware and found HuRUpdater.
Here the step-by-step tutorial:
1) download version B310
2) rename files (required by HuRUpdater):
- update_data_full_public.zip -> update_data_public.zip
- update_full_BTV-DL09_hw_eu.zip -> update_all_hw.zip
3) download HuRUpdater, I used version 0.3 if a new is available read what's changed.
4) (optional) download custom recovery (in this case the Greatslon TWRP for EMUI 5) and rename it "recovery.img"
5) copy all files to SD, in a subfolder (don't use "dload")
6) install, if not already present, the custom recovery
7) boot to the recovery and install "HuRUpdater_0.3.zip"
8) follow on-screen instructions than reboot!
At this point the Mediapad was working BUT
A) without root
B) with a "half" lock: the bootloader says it's unlocked but refused to flash or boot a custom recovery.
Problem B: I had to re-unlock the booloader with command
fastboot oem unlock 12345678901234567980
I accepted that my data will be erased (I have a backup, you too???) and the Mediapad rebooted.
I was lucky because the data was not erased and the bootloader now was fully unlocked. I'm not sure if this works for all of you so backup your data before. (***)
Problem A: not the custom recovery is booting so I flashed Magisk 15.3 (I had this version on other devices and don't wanted to do more testing for that day). It installed correctly, rebooted and
that's all folks!
(***) Here the enlightenment: https://forum.xda-developers.com/showpost.php?p=78194270&postcount=1029 from @zxz0O0
In short: flash also the custom recovery!
I have a M3 that can only boot up to twrp. I am trying to fix this tablet, since the previous owner accidentally erased the system partition, and it will not load. I did a search using the firmware finder, but wasn't sure I did it right, alot of versions came up. I do not know what software version was on it, before it got messed up. All I know is that it was bought less than two months ago. I was hoping someone could post a direct link to the firmware that I could use to get this tablet up and running again. the original owner lives in the US, as do I. Any help will be greatly appreciated. Thanks in advance
thew-tab said:
I have a M3 that can only boot up to twrp. I am trying to fix this tablet, since the previous owner accidentally erased the system partition, and it will not load. I did a search using the firmware finder, but wasn't sure I did it right, alot of versions came up. I do not know what software version was on it, before it got messed up. All I know is that it was bought less than two months ago. I was hoping someone could post a direct link to the firmware that I could use to get this tablet up and running again. the original owner lives in the US, as do I. Any help will be greatly appreciated. Thanks in advance
Click to expand...
Click to collapse
First you need to know the exact model. One method can be this:
0) insert an SD card
1) boot the TWRP
2) open the terminal
3) execute the command:
Code:
dd if=/dev/block/bootdevice/by-name/oeminfo of=/external_sd/oeminfo.img
this will copy the OEMINFO partition to the SD card.
4) open the oeminfo.img file with a hex editor and search for "BTV", do not stop to the first occurrence: there are some and you will find the exact firmware code that was installed.
5) search a FULL firmware with FW finder than flash it!
Nicola
nicolap8 said:
First you need to know the exact model. One method can be this:
0) insert an SD card
1) boot the TWRP
2) open the terminal
3) execute the command:
Code:
dd if=/dev/block/bootdevice/by-name/oeminfo of=/external_sd/oeminfo.img
this will copy the OEMINFO partition to the SD card.
4) open the oeminfo.img file with a hex editor and search for "BTV", do not stop to the first occurrence: there are some and you will find the exact firmware code that was installed.
5) search a FULL firmware with FW finder than flash it!
Nicola
Click to expand...
Click to collapse
Hello. I messed up my M3 trying to update and now Bluetooth does not work.
My firmware shows in Settings as "testkeys", so I don't really now what firmware is, probably B302 since security patch is from November 2017.
I am trying to flash full firmware again and do a full wipe. I tried to do it via TWRP and eRecovery too, but both methods fail.
I also tried the method the OP mentioned with no luck either (maybe because mine is the WiFi-only European version).
What should I do? How do I go back to stock? I don't care if I lose my data or if I have to relock bootloader again, I just want my M3 to work properly again!
sergio_sant said:
Hello. I messed up my M3 trying to update
Click to expand...
Click to collapse
Exact model?
Exact firmware that you have?
nicolap8 said:
Exact model?
Exact firmware that you have?
Click to expand...
Click to collapse
Model is BTV-W09C100B006 according to oeminfo.img, so I guess firmware must be B006?
In Settings it shows up like the screenshot attached:
sergio_sant said:
Model is BTV-W09C100B006 according to oeminfo.img, so I guess firmware must be B006?
In Settings it shows up like the screenshot attached:
Click to expand...
Click to collapse
Ahi, ahi... you are unable to discriminate what is the device model (BTV-W09) from the firmware version (BTV-W09C100B006). So you are not enough experienced nor skilled... Search someone that can help you offline!
nicolap8 said:
Ahi, ahi... you are unable to discriminate what is the device model (BTV-W09) from the firmware version (BTV-W09C100B006). So you are not enough experienced nor skilled... Search someone that can help you offline!
Click to expand...
Click to collapse
I may be not enough experienced nor skilled but I've been unlocking, rooting and changing roms to my phones since Android 2.1 era, that was many years ago as you know.
I know that the model is BTV-W09, I just said that OEMINFO says BTV-W09C100B006 when searching "btv" with an hex-editor following YOUR instructions from your earlier post.
Anyway, thanks for nothing, I finally found a solution by myself writing the required images one by one trough ADB.
Have a nice day.
I had to have messed up something quite well, I ran the updater, everything seemed to go fine, but when I rebooted, it wont go off the Huawei MediaPad android screen, and I can not get it back into TWRP , or get it to do anything else, any help would be greatly appreciated.
nicolap8 said:
First you need to know the exact model. One method can be this:
0) insert an SD card
1) boot the TWRP
2) open the terminal
3) execute the command:
Code:
dd if=/dev/block/bootdevice/by-name/oeminfo of=/external_sd/oeminfo.img
this will copy the OEMINFO partition to the SD card.
4) open the oeminfo.img file with a hex editor and search for "BTV", do not stop to the first occurrence: there are some and you will find the exact firmware code that was installed.
5) search a FULL firmware with FW finder than flash it!
Nicola
Click to expand...
Click to collapse
thew-tab said:
I had to have messed up something quite well, I ran the updater, everything seemed to go fine, but when I rebooted, it wont go off the Huawei MediaPad android screen,
Click to expand...
Click to collapse
Explain better, which screen?
and I can not get it back into TWRP , or get it to do anything else, any help would be greatly appreciated.
Click to expand...
Click to collapse
Reread first post.
It is the initial boot screen
nicolap8 said:
Explain better, which screen?
Reread first post.
Click to expand...
Click to collapse
Model?
Firmware previously on tablet?
Firmware that you installed?
Which files you used?
The update procedure was successfully or there was some message?
Model number is BTV-W09
Do not know the original firmware, but I apparently read the model number wrong when I looked it up. I used BTV-DL09. TWRP said install was a success ( I used the HuRUupdater thru TWRP) The files used was the full OTA , the update_full_BTV-DL09_dialcu_cn.zip, as well as the update_data_full_public.zip. I changed the file name to the names that were needed to run HuRUpdater. So my question is does anyone know how to fix my mistake?
I was able to get it into fastboot mode, but it said the phone was locked, and was not picked up by my computer.
nicolap8 said:
Model?
Firmware previously on tablet?
Firmware that you installed?
Which files you used?
The update procedure was successfully or there was some message?
Click to expand...
Click to collapse
thew-tab said:
Model number is BTV-W09
I used BTV-DL09. TWRP said install was a success
Click to expand...
Click to collapse
NEVER install the software for one model on a different hardware. NEVER!
What TWRP says it's not important: it only wrote some files on a disk but it's not of interest what is inside these files.
You have to flash an appropriate firmware, no other options.
how can I flash the the firmware, if I no longer have TWRP, or when I can get into flashboot mode, the computer does not recognize the tablet? . Here is a probably stupid question: do I look for BTV-W09, which is the model of MY tablet?
nicolap8 said:
NEVER install the software for one model on a different hardware. NEVER!
What TWRP says it's not important: it only wrote some files on a disk but it's not of interest what is inside these files.
You have to flash an appropriate firmware, no other options.
Click to expand...
Click to collapse
thew-tab said:
how can I flash the the firmware, if I no longer have TWRP, or when I can get into flashboot mode. Here is a probably stupid question: do I look for BTV-W09, which is the model of MY tablet?
Click to expand...
Click to collapse
You have to unpack the firmware and flash the partition images with flashboot.
Search the forum for "Huawei Update Extractor".
which of these are the partition images? Second stupid question, I tried to get in to fastboot, but the computer would not recognize the tablet
nicolap8 said:
You have to unpack the firmware and flash the partition images with flashboot.
Search the forum for "Huawei Update Extractor".
Click to expand...
Click to collapse
thew-tab said:
which of these are the partition images? Second stupid question, I tried to get in to fastboot, but the computer would not recognize the tablet
Click to expand...
Click to collapse
All of this are partition images!
The problem is that you have to write all relevant partitions that was written from bad firmware!
Often boot.img is enough to have TWRP working.
What about if I can't get the computer to recognize the tablet in fastboot mode?
nicolap8 said:
All of this are partition images!
The problem is that you have to write all relevant partitions that was written from bad firmware!
Often boot.img is enough to have TWRP working.
Click to expand...
Click to collapse
This is the screen I see when I am in flashboot mode
thew-tab said:
What about if I can't get the computer to recognize the tablet in fastboot mode?
Click to expand...
Click to collapse