Related
I have one of the newer TF101's (B90). I had the Revolver ROM installed on it. I encrypted the tablet. I attempted to install the stock ROM back on the device, which also wiped out CWM and reinstalled the stock recovery. Here's the thing: The original password I had does not work on the device anymore, and the tablet is seemingly still encrypted. I cannot boot into UPX (probably due to the HW version), and the recovery ROM only displays the ! graphic.
Is there anything I can do?
whatexcusenow said:
I have one of the newer TF101's (B90). I had the Revolver ROM installed on it. I encrypted the tablet. I attempted to install the stock ROM back on the device, which also wiped out CWM and reinstalled the stock recovery. Here's the thing: The original password I had does not work on the device anymore, and the tablet is seemingly still encrypted. I cannot boot into UPX (probably due to the HW version), and the recovery ROM only displays the ! graphic.
Is there anything I can do?
Click to expand...
Click to collapse
You need to wipe the data partition. This isn't windows. This is android. In windows, you have 1 big partition so reinstalling the OS kills everything. In android, there are over a dozen different partitions. Installing a new OS doesn't touch the data partition. And since revolver is based on the stock, some data will still work in the stock, like your encryption.
You need to nvflash in the cwm and use it to wipe the data.
goodintentions said:
You need to nvflash in the cwm and use it to wipe the data.
Click to expand...
Click to collapse
but he has a B90 so no NVFlash
Oh, didn't see that part.
I am constantly amazed at people refusing (for religious reason or whatever reason) to wipe data before flashing another rom and then complain that something is wrong.
Someone else might be able to help. In the mean time, let me think about this one.
You can follow the Unroot Process, which will wipe /Data (also your /SDCARD) - you're already through the first part since you have the stock recovery installed.
Just download the stock firmware from Asus' website and follow the instructions in the "Updated Version of SOP" manual (also from Asus' website) - it involves using an micro-sd card and extracting the stock firmware to it, then booting to Recovery. The stock recovery should automagically find the firmware update and flash it.
Edit: Edited for clarity, and added a link to the download's page - http://support.asus.com/Download.aspx?SLanguage=en&m=Eee+Pad+Transformer+TF101&p=20&s=16
hold vol down, wait until it asks about data wipe, press vol up, wait a few minutes while it does the datawipe
HI, i have been having isues with my asus tf101 baterry, about one month ago it suddenly charge and discharges, like: 10%-25%-40%-70%-80%-100%...I made a factory reset but nothing. 2 weeks ago, it solved alone, without do anything, and was ok for 2 weeks, now again i have the problem..
i have installed cwm recovery, i want to change to android revolution rom, to see if the problem finish:
1 question: How i change from cwm to twrp recovery? installing twrp from cwm using a zip? is there no problem?? or downloading goomanager, installing recovery script?? Is there any problem to use cwm or twrp( i have read, to instal kk i dont use cwm)?
2 question, what rom is stable to try to solve this? i see kk 4.3 etc, but i just one my baterry works ok...
3 question, is there any way to clean absolutely the stock rom? i tried wipe cache, dalvik, factory reset(again) but nothing solve.
4 question, is possible to wipe ALL including system, and install the asus stock rom using zip¿?
Thanks for your atention, please be the most specifically possible because i am new on this, and i just one my tablet for study(read books).
I have a asus tf101 b70 root, with CWM recovery is a old version 5.0.26 something..
cesar_cjx said:
HI, i have been having isues with my asus tf101 baterry, about one month ago it suddenly charge and discharges, like: 10%-25%-40%-70%-80%-100%...I made a factory reset but nothing. 2 weeks ago, it solved alone, without do anything, and was ok for 2 weeks, now again i have the problem..
i have installed cwm recovery, i want to change to android revolution rom, to see if the problem finish:
1 question: How i change from cwm to twrp recovery? installing twrp from cwm using a zip? is there no problem?? or downloading goomanager, installing recovery script?? Is there any problem to use cwm or twrp( i have read, to instal kk i dont use cwm)?
2 question, what rom is stable to try to solve this? i see kk 4.3 etc, but i just one my baterry works ok...
3 question, is there any way to clean absolutely the stock rom? i tried wipe cache, dalvik, factory reset(again) but nothing solve.
4 question, is possible to wipe ALL including system, and install the asus stock rom using zip¿?
Thanks for your atention, please be the most specifically possible because i am new on this, and i just one my tablet for study(read books).
I have a asus tf101 b70 root, with CWM recovery is a old version 5.0.26 something..
Click to expand...
Click to collapse
Q1: I think you can just flash the new recovery via the current recovery if you have the new recover zip file.
Q2: Kat Kiss works fine for me.
Q3: If you want to completely return to stock, you would have to use NVFlash. There are tons of instructions on the Dev thread. I primarily use Tubuntu for flashing with NVFlash. [http://forum.xda-developers.com/showthread.php?t=1995157]
You can find other images as well. I used a stock image once to RMA the tablet but now I'm not sure where I got it. This method will ensure that every bit in your memory is exactly as it left the factory. Including the bootloader, recovery partition and everything else.
Q4: Refer Q3.
Download flashable TWRP 2.6.3.11 zip for TF101:
http://forum.xda-developers.com/devd...ct/dl/?id=3280
You should use TWRP for KatKiss ROMs, do not use CWM
Flash that Zip from CWM then reboot fully into your current ROM, then reboot into Recovery to check it has flashed properly
From TWRP you can wipe everything and flash KatKiss & Gapps
*Detection* said:
Download flashable TWRP 2.6.3.11 zip for TF101:
http://forum.xda-developers.com/devd...ct/dl/?id=3280
You should use TWRP for KatKiss ROMs, do not use CWM
Flash that Zip from CWM then reboot fully into your current ROM, then reboot into Recovery to check it has flashed properly
From TWRP you can wipe everything and flash KatKiss & Gapps
Click to expand...
Click to collapse
Is this the same process for going from TWRP to TWRP? just "install" the newest version from recovery and do the reboots?
stache12 said:
Is this the same process for going from TWRP to TWRP? just "install" the newest version from recovery and do the reboots?
Click to expand...
Click to collapse
Yep, so long as you reboot into your ROM after flashing the new TWRP before booting back into recovery
Thanks for your reply, i will tray soon. So i want to clean the asus stock room to see if battery goes ok, i tried wipe data, cache, dalvik, with cwm, but nothing.
If i install twrp what more options can i try before change the rom? what more wipe do i need?? and finally, if i change the rom, is possible to go back to asus stock just flashing from recovery? or how should i do?
Apart from wiping the ROM (SYSTEM) there's not much else you can wipe, you could try wiping the same as you have already done, but from TWRP, see if that makes any difference, maybe the battery is coming to the end of its life
You can flash stock ASUS ROMs back again from TWRP yes, but you will wipe your recovery & ROM back to 100% stock by doing it
Best thing to do is to make a full Nandroid Backup from TWRP before flashing any custom ROMs, save it to MicroSD Card, then if you want to go back to the way it is now, just restore the backup from TWRP
That way you keep TWRP and can switch between as many ROMs as you like and always have your stock backup to go back to whenever you want
46999589
*Detection* said:
Apart from wiping the ROM (SYSTEM) there's not much else you can wipe, you could try wiping the same as you have already done, but from TWRP, see if that makes any difference, maybe the battery is coming to the end of its life
You can flash stock ASUS ROMs back again from TWRP yes, but you will wipe your recovery & ROM back to 100% stock by doing it
Best thing to do is to make a full Nandroid Backup from TWRP before flashing any custom ROMs, save it to MicroSD Card, then if you want to go back to the way it is now, just restore the backup from TWRP
That way you keep TWRP and can switch between as many ROMs as you like and always have your stock backup to go back to whenever you want
Click to expand...
Click to collapse
Thanks!! I will try, but apart from wipe system(rom) what more wipes can i try without erase the rom?..I think not, because a week ago the battery was perfect working...i hope so.
CACHE,
DALVIK CACHE,
FACTORY RESET,
INTERNAL STORAGE,
FORMAT DATA
Only other 2 options are SYSTEM & EXTERNAL STORAGE
Hi!
A while back I had some issues with the phone, it was when I was supposed to boot it, it always took 2 tries. It always got stuck, then had to long press the lock key to hard reboot it, then it worked fine. This prevented me from doing a factory reset (in hope to fix (what I later found out was) a media rescan etc). Tried to root it, something happened and it wouldn't boot anymore. Yiti yata and the phone wouldn't boot. Finally I got it back to life with some guide on here and I used whatever 4.4.4 I downloaded.
The software wouldn't find any "normal" update phone updates, so I figured I would try Resurrection Remix 7.1.x (.2 I think it was). At first I got just that it failed with some 2.x twrp version. Updated to TWRP 3.1.x.x (3.1.1.0 if I guess). Now I got to know that it was a TZ error (ERROR 7) from TWRP. This happened to my "RR-N-v5.8.3-20170718-bacon-Official.zip" file. I managed to get around it by doing this: https://forum.xda-developers.com/showthread.php?t=2522762. So I could get this installed, sort of I think. The problem now was that it would show the very first oneplus boot screen for around 20 ish seconds, before it would reboot in a boot loop.
So I tried to install some other CM Lineage Os nightly thing (they said install that and then RR), but that didn't work either. This post was the one I donwloaded from (install this first, then RR should work).
I tried doing this both on TWRP 2.8.6.0 and 3.1.1.0 since I saw some post about the modem not being right from versions newer than 2.8.6.0.
Looking around a bit more I saw in some post someone talking about firmware..? Does this matter anything, also how is this different from the recovery or ROM? (new to this stuff)
In short, last working version of Android I had on there was 4.4.4 (think I followed this post). Using a Mac currently and have no problem with flashing, entering fastboot or recovery.
My procedure when I tried to install RR was:
Install the TWRP 3.1.1.0 or 2.8.6.0 (since I did it several times).
Wipe everything (Have nothing of value on the phone) cache, system, internal storage, dalvik and data. Also did a factory reset (from TWRP) before if that matters.
Copied RR and Gapps 7.1 ARM (not arm64) over.
Installed RR, wiped cache/dalvik. (or linear/cm (post above^^) when I tried that)
Installed Gapps, wiped cache/dalvik.
Boot loop.
Also tried with/without emptying cache/dalvik also chose to install both zips at once.
So can anyone clue in how I can proceed to get RR 7.1 onto my OPO? Any help is very much appreciated
I'm sorry if this wasn't the best post. Have an immense headache at the moment
wahlmat said:
Hi!
A while back I had some issues with the phone, it was when I was supposed to boot it, it always took 2 tries. It always got stuck, then had to long press the lock key to hard reboot it, then it worked fine. This prevented me from doing a factory reset (in hope to fix (what I later found out was) a media rescan etc). Tried to root it, something happened and it wouldn't boot anymore. Yiti yata and the phone wouldn't boot. Finally I got it back to life with some guide on here and I used whatever 4.4.4 I downloaded.
The software wouldn't find any "normal" update phone updates, so I figured I would try Resurrection Remix 7.1.x (.2 I think it was). At first I got just that it failed with some 2.x twrp version. Updated to TWRP 3.1.x.x (3.1.1.0 if I guess). Now I got to know that it was a TZ error (ERROR 7) from TWRP. This happened to my "RR-N-v5.8.3-20170718-bacon-Official.zip" file. I managed to get around it by doing this: https://forum.xda-developers.com/showthread.php?t=2522762. So I could get this installed, sort of I think. The problem now was that it would show the very first oneplus boot screen for around 20 ish seconds, before it would reboot in a boot loop.
So I tried to install some other CM Lineage Os nightly thing (they said install that and then RR), but that didn't work either. This post was the one I donwloaded from (install this first, then RR should work).
I tried doing this both on TWRP 2.8.6.0 and 3.1.1.0 since I saw some post about the modem not being right from versions newer than 2.8.6.0.
Looking around a bit more I saw in some post someone talking about firmware..? Does this matter anything, also how is this different from the recovery or ROM? (new to this stuff)
In short, last working version of Android I had on there was 4.4.4 (think I followed this post). Using a Mac currently and have no problem with flashing, entering fastboot or recovery.
My procedure when I tried to install RR was:
Install the TWRP 3.1.1.0 or 2.8.6.0 (since I did it several times).
Wipe everything (Have nothing of value on the phone) cache, system, internal storage, dalvik and data. Also did a factory reset (from TWRP) before if that matters.
Copied RR and Gapps 7.1 ARM (not arm64) over.
Installed RR, wiped cache/dalvik. (or linear/cm (post above^^) when I tried that)
Installed Gapps, wiped cache/dalvik.
Boot loop.
Also tried with/without emptying cache/dalvik also chose to install both zips at once.
So can anyone clue in how I can proceed to get RR 7.1 onto my OPO? Any help is very much appreciated
I'm sorry if this wasn't the best post. Have an immense headache at the moment
Click to expand...
Click to collapse
Calm down.
You're right about that firmware thing,that is the one causing issue when you're trying to flash RR 5.8.3 over KitKat.
This is because the firmware that kitkat comes with,is old and don't support newer android versions,that's because it is made for KitKat only.
Always use latest Twrp(https://dl.twrp.me/bacon/).
Make sure you don't edit any zip like what you did with the Rom zip earlier(devs don't post non-working zips),I'm sure you've a backup of your non-edited zip,if not,re-download the zip.
Now boot into latest twrp,wipe everything except internal storage.
Firmware: https://drive.google.com/file/d/0BxysuRdzsJeWeW9JbTNwaUJKb1E/view?usp=drivesdk
Flash the above zip,then without wiping anything flash rom zip(unedited) then flash google apps package(opengapps.org)(optional).
Reboot.It should boot fine now.
Good luck!
Mr.Ak said:
Calm down.
You're right about that firmware thing,that is the one causing issue when you're trying to flash RR 5.8.3 over KitKat.
This is because the firmware that kitkat comes with,is old and don't support newer android versions,that's because it is made for KitKat only.
Always use latest Twrp(Can't post links withing 10 posts apparently...).
Make sure you don't edit any zip like what you did with the Rom zip earlier(devs don't post non-working zips),I'm sure you've a backup of your non-edited zip,if not,re-download the zip.
Now boot into latest twrp,wipe everything except internal storage.
Firmware:
Flash the above zip,then without wiping anything flash rom zip(unedited) then flash google apps package(Can't post links withing 10 posts apparently...)(optional).
Reboot.It should boot fine now.
Good luck!
Click to expand...
Click to collapse
Thank you so much! Got it working on 1st try with what you provided! Seems like the firmware thing was the bad guy in this scenario. A little interest, what specifically is the firmware in this case? Either way, rocking RR now and I'm really grateful
wahlmat said:
Thank you so much! Got it working on 1st try with what you provided! Seems like the firmware thing was the bad guy in this scenario. A little interest, what specifically is the firmware in this case? Either way, rocking RR now and I'm really grateful
Click to expand...
Click to collapse
I'm glad you got it up and running.
Here are some FAQs:
What is a Firmware? What is Modem?
- Firmware is the whole package of proprietary partitions of your device, modem itself is a NON-HLOS file responsible for your device's communications over Wi-Fi, Mobile Networks and other such stuff.
So what is the difference between firmware and ROM then?
- Firmware is the responsible partition for IMEIs, the modemst partitions hold your IMEI, persist holds your Mac addresses etc.
ROM is only a combination of system.img and boot.img (kernel)
What to restore if I loose my IMEI?
- Both the modemst partitions (IMP: considering you took a backup of them before)
What is the default firmware? (default= firmware which comes with the latest CM/ LineageOS 14.1 weeklies)
- c6-00241
Thanks a lot, once again
Help!
I'm not sure of all the specifics on my oneplus one but I accidentally updated the wrong update from my nightly bacon.. it now is stuck in Boot Loop I can get to the fastboot screen (it gets stuck there too) and I can get to the recovery, etc (but it is not the usual screen with all the folders (it was rooted).. it is now just four options in Cyanogenmod recovery.. none work. I do not want to lose my data :crying: .. Sadly my techy is not available to save me! Please help this untechy Cali Girl! I've googled and researched and its still like a foreign language.. Thank you!!
HisMuse said:
I'm not sure of all the specifics on my oneplus one but I accidentally updated the wrong update from my nightly bacon.. it now is stuck in Boot Loop I can get to the fastboot screen (it gets stuck there too) and I can get to the recovery, etc (but it is not the usual screen with all the folders (it was rooted).. it is now just four options in Cyanogenmod recovery.. none work. I do not want to lose my data :crying: .. Sadly my techy is not available to save me! Please help this untechy Cali Girl! I've googled and researched and its still like a foreign language.. Thank you!!
Click to expand...
Click to collapse
I am not 100% sure, but I would say, boot into fastboot, flash something like TWRP recovery, then you will be able to access the device files from the recovery. Just reflashing the boot shouldn't mess up anything as far as I am concerned. After that (when you've grabbed all the files you want), flash the newest firmware the guy linked above and install your latest 7.0 ROM
wahlmat said:
I am not 100% sure, but I would say, boot into fastboot, flash something like TWRP recovery, then you will be able to access the device files from the recovery. Just reflashing the boot shouldn't mess up anything as far as I am concerned. After that (when you've grabbed all the files you want), flash the newest firmware the guy linked above and install your latest 7.0 ROM
Click to expand...
Click to collapse
I can get phone to fastboot but it just stays on the screen that says fastboot.. do I need a computer?
HisMuse said:
I can get phone to fastboot but it just stays on the screen that says fastboot.. do I need a computer?
Click to expand...
Click to collapse
Yes you do. You need that + some software. Check out some "install custom recovery oneplus one" guides, you should be able to find something. Are you on Mac or Windows?
Yes I'm on Windows 10.. I tried removing battery overnight as well .. its not boiling hot anymore but still stuck in bootloop.
HisMuse said:
Yes I'm on Windows 10.. I tried removing battery overnight as well .. its not boiling hot anymore but still stuck in bootloop.
Click to expand...
Click to collapse
Download the Samsung ADB driver or whatever it was called, then flash a new recovery for it. There are multiple guides for doing that. After that you should be able to transfer your files to your pc while being in recovery mode
Hello,
I am running PixysOS rom on my Honor 6X (BLN-AL20) since some months and I am actually satisfied of the stability and usability of the Rom.
Actually I can't convince the device to use the installed as card to store pictures, videos etc.
The SD card is recognised and listed under memory but the system is not using it.
Is there any workaround to fix this problem?
Thanks,
Andrea.
Sent from my BLN-AL20 using Tapatalk
Anybody out there?
Sent from my BLN-AL20 using Tapatalk
Sephiroth79 said:
Anybody out there?
Sent from my BLN-AL20 using Tapatalk
Click to expand...
Click to collapse
for me my internal storage is not detected. only sd card is main storage. seems like its a bug and never gonna fixed. there is no perfect android 9 os out there. so better go to emui 8 and use cyclox kernel.
Sephiroth79 said:
Hello,
I am running PixysOS rom on my Honor 6X (BLN-AL20) since some months and I am actually satisfied of the stability and usability of the Rom.
Actually I can't convince the device to use the installed as card to store pictures, videos etc.
The SD card is recognised and listed under memory but the system is not using it.
Is there any workaround to fix this problem?
Thanks,
Andrea.
Click to expand...
Click to collapse
By what I read in the thread of DotOS, that's a bug that should had be fixed in latest builds... Are you using latest version or not?
Anyway every Pie ROM/GSI I tried seems to read microSD, eject it and re-read once again immediately after booting to OS, on every single boot. Then, there are systems that keep reading the microSD (as AEX, Descendant...) and allows modifications, reading files, basically everything you should be able to do with a microSD, and systems that just keep it ejected (like DotOS did on old builds). Saw other users reporting that on the thread. Look for "microSD" in DotOS thread to read latest comments about, there you could find a solution. By how things sound at the moment, my only advice is to move on another system.
Thanks for your reply. Could you suggest me a proper and stable rom?
Sephiroth79 said:
Thanks for your reply. Could you suggest me a proper and stable rom?
Click to expand...
Click to collapse
Nothing hard to do man. We use to thank others with the appropriate button, for next times.
Anyway since that we're not talking 'bout different devices but we share the same phone, i feel to strongly recommend ya the Descendant GSI project by Dil3mm4.. It's a fork of Phh AOSP project but with sone very good extras. I never used a system smooth like this one, really impressive. It has a decent amount of customizations options (not at levels like RROS in example, but too much is too much IMHO), great battery management, fluid transitions and great compatibility with Huawei devices (it's a GSI, but the dev has a P8 Lite at the moment, so he knows how to make things working on Huawei).
Give it a shot, you can always go back to stock with HuRUpdater in just 5 minutes. And in case you'd like to try more, remember to take a look into Treble section here on XDA. Every arm64 a-only GSI is good to be flashed on our device, but before flashing just look if other users owning a Huawei device have already tried it or not. I say this simply because many GSIs are actually not working thanks to our vendor compatibility, so make things without hurry and nothing can go wrong
Used appropriate "thanks button" this time...eheh
Any tutorial on how to install the Descendant GSI rom starting from PixysOs with Askuccio's TWRP?
Sephiroth79 said:
Used appropriate "thanks button" this time...eheh
Any tutorial on how to install the Descendant GSI rom starting from PixysOs with Askuccio's TWRP?
Click to expand...
Click to collapse
Well there isn't a dedicated tutorial for every ROM/GSI you're starting from, overall because a clean flash is strongly recommended (especially when you switch from a ROM to a GSI) - you can dirty flash Descendant updates or other GSIs based on phhusson trees without problems, but in this case you've already modified your device kernel and other stuff with a custom ROM, so it's better to start from scratch in way to avoid useless wastes of time running to repairs with hurry.
The faster and safest way to do this is:
1) restore stock OS with HuRUpdater and let it boot (i saw that you already own Askuccio's TWRP, i always had to use Elemental TWRP from KingOfMezi in way to use HuRU without errors, but apart this Askuccio's TWRP works for flashing everything you'd need);
2) following steps listed in Descendant OP, flash the system image through fastboot or through TWRP, then reboot to TWRP once again and wipe ONLY /cache and /dalvikART partitions;
3) factory reset through stock recovery and let the system boot (yeah, you'll have to reflash stock recovery once again before reflashing TWRP - again.
4) flash all the rest you'd like to flash (GApps, Magisk, ecc.)
By default, /data partition remains encrypted after performing factory reset with stock recovery, and so with TWRP you won't be able to perform full backups, but you can also choose to run with /data decrypted. The method isn't supported by the developer, but works like a charm (personally tested about 3 versions of the GSI ago, worked). You just have to flash "disable dm verity" script during the process, but you can know more by reading about it here.
Happy flashing
RedSkull23 said:
Well there isn't a dedicated tutorial for every ROM/GSI you're starting from, overall because a clean flash is strongly recommended (especially when you switch from a ROM to a GSI) - you can dirty flash Descendant updates or other GSIs based on phhusson trees without problems, but in this case you've already modified your device kernel and other stuff with a custom ROM, so it's better to start from scratch in way to avoid useless wastes of time running to repairs with hurry.
The faster and safest way to do this is:
1) restore stock OS with HuRUpdater and let it boot (i saw that you already own Askuccio's TWRP, i always had to use Elemental TWRP from KingOfMezi in way to use HuRU without errors, but apart this Askuccio's TWRP works for flashing everything you'd need);
2) following steps listed in Descendant OP, flash the system image through fastboot or through TWRP, then reboot to TWRP once again and wipe ONLY /cache and /dalvikART partitions;
3) factory reset through stock recovery and let the system boot (yeah, you'll have to reflash stock recovery once again before reflashing TWRP - again.
4) flash all the rest you'd like to flash (GApps, Magisk, ecc.)
By default, /data partition remains encrypted after performing factory reset with stock recovery, and so with TWRP you won't be able to perform full backups, but you can also choose to run with /data decrypted. The method isn't supported by the developer, but works like a charm (personally tested about 3 versions of the GSI ago, worked). You just have to flash "disable dm verity" script during the process, but you can know more by reading about it here.
Happy flashing
Click to expand...
Click to collapse
Point 1: I have to download stock fw using Huawei firmware finder and I have to use Askuccio's TWRP to flash HuRupdater on the device. Do I have to choose a custom recovery or I have to let HuRupdater flash stock recovery too?
Point 2: you are saying I have to wipe cache/dalviw partitions using TWRP so I have to flash TWRP after flashing and booting stock fw?
Sephiroth79 said:
Point 1: I have to download stock fw using Huawei firmware finder and I have to use Askuccio's TWRP to flash HuRupdater on the device. Do I have to choose a custom recovery or I have to let HuRupdater flash stock recovery too?
Point 2: you are saying I have to wipe cache/dalviw partitions using TWRP so I have to flash TWRP after flashing and booting stock fw?
Click to expand...
Click to collapse
To me flashing HuRU with Askuccio TWRP never worked, as said above, so i'd suggest you to look for ElementalTWRP in way to have a custom recovery that can flash HuRU with no problems. Secondarily, in way to avoid confusion, just start from stock and do a fastboot flash of Descendant, reboot to OS and let it boot. Once set, flash TWRP and flash GApps, then wipe just /cache and /dalvik and reboot one last time. Then you can do anything you want.
RedSkull23 said:
To me flashing HuRU with Askuccio TWRP never worked, as said above, so i'd suggest you to look for ElementalTWRP in way to have a custom recovery that can flash HuRU with no problems. Secondarily, in way to avoid confusion, just start from stock and do a fastboot flash of Descendant, reboot to OS and let it boot. Once set, flash TWRP and flash GApps, then wipe just /cache and /dalvik and reboot one last time. Then you can do anything you want.
Click to expand...
Click to collapse
Ok, I'll put elemental TWRP recovery in the same directory in order to let HuRU flash it together with the stock firmware.
Edit: can't find elemental twrp download link
Sephiroth79 said:
Ok, I'll put elemental TWRP recovery in the same directory in order to let HuRU flash it together with the stock firmware.
Edit: can't find elemental twrp download link
Click to expand...
Click to collapse
Good, i usually do that later just in case the system prompts to factory reset before booting, but it's up to you. Here's the link anyway https://mega.nz/#!a81EDZAR!2-9yPFh3reghkGcfSl3nRIJhHGkP8fqDsgUG66ewjkk
Using fw finder I downloaded the fw named: BLN-AL30C00B541 (8.0.0.541) FULLOTA-MF 2018.12.27
Clicking on download give me some choices:
- update.zip (1.74 GB)
- BLN-Al20_all_cn/update_full_BLN-AL20_all_cn.zip (643 MB)
Already downloaded both of them and can't find any of the files required from HurUpdater to run. Do I have to use an extractor?
EditOne: used Huawei Update Extractor gives an error on the update.app extracted from the update.zip archive and works on the same file extracted from BLN-Al20_all_cn/update_full_BLN-AL20_all_cn.zip
Edit2: just realized I don't need to extract anything but still can't find update_data_public and update_all_hw files
That is because it's Chinese build and as you just noticed some update packages are assembled in a slightly different manner, so some package misses one if not two useful zips. Would you mind to switch to India variant? Nothing changes in performance nor in features, plus if you'd only use the firmware as a base to get to other ROMs/GSIs, it really doesn't matter (but i can offer better assistance since that i'm more experienced with India variant other than China). FYI in this thread https://forum.xda-developers.com/honor-6x/how-to/french-language-t3938592/ i've already guided an user to obtain India variant, but it's really simple:
in TEAM MT site (google for "team mt online firmware database", the first result you get is what you need), look for build "BLN-L22HNC675CUSTC675D1B510" - you'll obtain 4 results. Download the package dated 2018.07.19, it is the better one. From here you just have to follow instructions in HwOTA thread, renaming the three packages as suggested in OP and choosing to debrand during the process to BLN-L22 region/variant (don't remember if it happens anyway since that the firmware is India variant but it's a thing that doesn't give hassles).
Hi guys. Last days I decided to try out some custom kernel with my MIUI ROM. I installed Genom kernel after having some problems installing the wrong AOSP version, but finally found the MIUI version on Telegram. When I tried to restore my backup (stock kernel) with Pitch-Black recovery, I noticed that Wifi and Bluetooth weren't working, flashing original firware fixed bluetooth but no wifi, then I had to go back to Genom kernel. Today I found a supposed MIUI stock kernel in the Genom kernel thread, but after flashing it I have bootloop. I can't wipe data, because I installed the Pitch-Black recovery from a different way, without mounting data (I didn't want to lost my data), I installed root from external storage, now I see it was a bad idea. The only thing that lasts is to install the full MIUI ROM again, but I just found the MIUI 10.3.2 for download, my device was running 10.3.3, and I'm afraid I can't install it or it to not work. Can someone give me a solution?
EDIT: I managed to wipe the Data, now I have access to internal storage, but I also wiped the system partition, so now I have no system installed. If I reboot my phone it will brick?
Tried to download the MIUI 10.3.2 firware from Xiaomi site, it has 2.5GB, but the download always fails at 2GB. I tried to install Pixel Experience ROM and Havoc-OS, both give me "Updater process ended with ERROR 7". I don't know what to do, my phone is unusable.