Database Info

please help me i have 701l and updat it to 703 and lose network

please help me i have 701l and updat it to 703 and lose network
i do
• Unlock Bootloader
• Flash X2_TWRP_CN_kangvip.rar
• Flash kangVIP b015 by TWRP
• Extract stock rom b015 and flash 4 img via fastboot
and lose network phone say no service what can i do if i Flash stock rom b106 via dload folder it will come up ?
or how can i return to GEM-701LV100R001C199B001

gaafar13 said:
please help me i have 701l and updat it to 703 and lose network
i do
• Unlock Bootloader
• Flash X2_TWRP_CN_kangvip.rar
• Flash kangVIP b015 by TWRP
• Extract stock rom b015 and flash 4 img via fastboot
and lose network phone say no service what can i do if i Flash stock rom b106 via dload folder it will come up ?
or how can i return to GEM-701LV100R001C199B001
Click to expand...
Click to collapse
You can go back to GEM-701LV100R001C199B001 via dload method.
Download GEM-701LV100R001C199B001 from http://4pda.ru/forum/lofiversion/index.php?t692755-100.html

eennap said:
You can go back to GEM-701LV100R001C199B001 via dload method.
Download GEM-701LV100R001C199B001 from
so can i contain and network will be come or no ?
and my baseband version is unknown is that normally
Click to expand...
Click to collapse

eennap said:
You can go back to GEM-701LV100R001C199B001 via dload method.
Download GEM-701LV100R001C199B001 from
Click to expand...
Click to collapse
so can i contain and network will be come or no ?
and my baseband version is unknown is that normally

now all thing is okay but emui information error like ram my ram is 2 now he write 1 resolution 540*960 android version 4.3 ???

now my phone on X2-B111_Kangvip
but my emui version 2
android version 4.3
ram 1
resolution 540*960
cpu quad core 1.2 ghz
can go back to GEM-701LV100R001C199B001 via dload method.

Just flash the universal Cust, and this will fix the false info "about the phone".
Did you go all the steps which I have described here? http://forum.xda-developers.com/showpost.php?p=64623653&postcount=378
I had tried to jump directly vom B106 to B111KangVIP, but it was not working properly.
If you try to install back the B001 you will perhaps loose the function to charge the battery. So be warned.
And by the way: my 701L had version B003. Are you sure your phone had B001? If yes ok. But if you have fully upgraded to Android 5.1.1 the flash of a lower version could produce unwanted effects.
After some experiments I restarted by flashing the B106 did a factory reset and then installed B109 and B111 stock via dload and then B111KangVIP. Then you will have back the full working machine and you will be happy.

audioralf said:
Just flash the universal Cust, and this will fix the false info "about the phone".
Did you go all the steps which I have described here? http://forum.xda-developers.com/showpost.php?p=64623653&postcount=378
I had tried to jump directly vom B106 to B111KangVIP, but it was not working properly.
If you try to install back the B001 you will perhaps loose the function to charge the battery. So be warned.
And by the way: my 701L had version B003. Are you sure your phone had B001? If yes ok. But if you have fully upgraded to Android 5.1.1 the flash of a lower version could produce unwanted effects.
After some experiments I restarted by flashing the B106 did a factory reset and then installed B109 and B111 stock via dload and then B111KangVIP. Then you will have back the full working machine and you will be happy.
Click to expand...
Click to collapse
where is the universal Cust ??? my phone had B001 my ask can i back the B001 or cant

You find univeral cust here: https://drive.google.com/file/d/0B5I_q70mNuR4VFhMc21DNGYtMHc/view?usp=sharing
You must flash it via 5.1.1 TWRP https://drive.google.com/file/d/0B5I_q70mNuR4Uy1XdXVoSG1SMXc/view?usp=sharing
If you already are on B111 the way back may lead you in disability to charge the battery. So most people here will say NO. That was also my experience. But you can try that and report, if you see the light and lightning icon for charging. This would be interesting.

audioralf said:
You find univeral cust here: https://drive.google.com/file/d/0B5I_q70mNuR4VFhMc21DNGYtMHc/view?usp=sharing
You must flash it via 5.1.1 TWRP https://drive.google.com/file/d/0B5I_q70mNuR4Uy1XdXVoSG1SMXc/view?usp=sharing
If you already are on B111 the way back may lead you in disability to charge the battery. So most people here will say NO. That was also my experience. But you can try that and report, if you see the light and lightning icon for charging. This would be interesting.
Click to expand...
Click to collapse
i will tray but if it cant charging can i return it ???
and which room hasn't Chinese language

Do a Backup in TWRP before you start the dload from the GUI.
If you have flashed the universalt cust you will see that the Andriod verson and storage Info will be correct.
But if did not go thru B106,B109,B111stock you will not have a full working Android 5.1.1. If this would be possible Huawiei would offer the dload for B111 if you are ond B106. No they don't. They inform you to upgrade to 109 via OTA or dload. When on B109 you will get the message tha there is a update for B111. So I guess we have to go that way, even if it seems that you have installed a B111. You have the wrong infos in the "about phone" and the universal cust is inside the B111KangVip.zip file. So this is curious. Start with flashing universal Cust, then flash 4 images for B106 and then go all steps via dload.

flashed the universalt cust and information still error

Do a Backup within TWRP (NANDROD) . Then do the dload after you have started the rom.
All ROMs for the 703 start in chinese, but you will be able to set the language. B111KANGVip has removed the most chinese.
---------- Post added at 10:45 PM ---------- Previous post was at 10:36 PM ----------
Ok if you still have the information error this is an indeed, that you must do all steps going thru all the fw versions.
Do that NANDROID of incomplete B111. If you have the "not charging problem" turn the device complete off to charge for a while. If it does not charge do a recover of the B111 to charge, then continue.
Start to install B106 and follow my instruction list http://forum.xda-developers.com/showpost.php?p=64623653&postcount=378

4. b This flashes GEM-703L official stock ROM b106 via dload folder. [This flash maybe abort on about (90-95%), but this does not effect the next steps] Wait to press ok until you have exchanged the dload folder for the next steps.
i wont do that setup restart and do nothing

gaafar13 said:
flashed the universalt cust and information still error
Click to expand...
Click to collapse
Do you have your original cust folder or your original rom? You may have a different cust folder based on your region and I can add your cust folder to the cust mod so when you flash it your information will be correct.

i reinstall all and still stuck in fouls information

ajsmsg78 said:
Do you have your original cust folder or your original rom? You may have a different cust folder based on your region and I can add your cust folder to the cust mod so when you flash it your information will be correct.
Click to expand...
Click to collapse
no i haven't what can i do

but i have all old info like Model IMEI Serial NR it can help

gaafar13 said:
no i haven't what can i do
Click to expand...
Click to collapse
If I had a link to download your original rom I could extract the cust from it and make it flashable.

i research for that room but cant find its call GEM-701LV100R001C199B001 please help me

How can i install older firmware in mt7-tl10

the phone was soft-bricked (boot-looping in the huawei initial animation), when i failed to instal correctly the update from b326 to b511, the bootloader was locked and the phone wasn't rooted, but i managed to solve both things, then i tried to restore a twrp backup of b511, since that was the version i tried to update to in the begining, after the restore, it was stuck yet again in boot loop but this time it only shows the initial huawei picture, so my cuestion is if there is some way to reinstall an older firmware, say b326, because when i did a backup so i could use the folder to store the files for the b511, the containing carpet name included b326, or if someone has a twrp backup for b326 that could share, it would be really apreciated
cheers
p.s.: i don't know if i should use some sort of rollback or how to use it, so any guidance would be really helpful
p.s.2: fooling around i just did another backup with twrp an it says that it has the b511 version, but i would love to go back to b326
p.s.3: i tried to run diferent stock recoveries and it only runs MM version, even when i flash recovery, boot, cache, cust, system and userdata from b326, it only let me run the MM recovery, aside of TWRP

nevermind, i finally solved it
so, with the b511 backup, you download it and change the s/n in the recovery txt, restore it with twrp and when you're going to reboot it, don't install the suggested SU, just let it run as it is and it will get into MM, then you flash the stock recovery using "recovery mate7 mobopx v2.1 translate by chudy_85" and follow the steps in this thread
http://forum.xda-developers.com/mate-7/development/finally-rollback-513-331-511-326-t3325803

Problem of switching back to Gem-702l android6.0

Hi,
I really need some help. My phone is gem-702l model, on B112 stock rom of 703l.
Now that Huawei has released a stock Android 6.0 (B201) for gem-702l, I am thinking about switching back.
Here are the thing I did and problem that stopped me.
1. I updated to B209 following the instruction in XDA without any problem.
2. When successfully on B209, I downloaded my stock B201 rom in Huawei website and extracted the 5 required img files: recovery, system, boot, cust, userdata
3. I fastboot flash the 5 img files and reboot. So far so good. The About Pone is correct except internal storage volume.
4. I factory reset and format the internal SD. Now everything in About Phone is correct.
5, I put the dload of b201 in my MicroSD. Strangely there's no "update from SD Card" option, So I use the three key(power, vol+/-)to hard flash the whole dload directory. It failed.
THe problem is : it seems that I can only fastboot flash 5 img files of 702l, there's no way of doing the whole dload update.
Now my phone is not fully converted to Gem-702l. it's kind of half 703l and half 702l in android 6.0.
Is there anything I missed or anything I can do to make it fully converted to 702l?
Please help! thank you so much.

iamhcg said:
Hi,
I really need some help. My phone is gem-702l model, on B112 stock rom of 703l.
Now that Huawei has released a stock Android 6.0 (B201) for gem-702l, I am thinking about switching back.
Here are the thing I did and problem that stopped me.
1. I updated to B209 following the instruction in XDA without any problem.
2. When successfully on B209, I downloaded my stock B201 rom in Huawei website and extracted the 5 required img files: recovery, system, boot, cust, userdata
3. I fastboot flash the 5 img files and reboot. So far so good. The About Pone is correct except internal storage volume.
4. I factory reset and format the internal SD. Now everything in About Phone is correct.
5, I put the dload of b201 in my MicroSD. Strangely there's no "update from SD Card" option, So I use the three key(power, vol+/-)to hard flash the whole dload directory. It failed.
THe problem is : it seems that I can only fastboot flash 5 img files of 702l, there's no way of doing the whole dload update.
Now my phone is not fully converted to Gem-702l. it's kind of half 703l and half 702l in android 6.0.
Is there anything I missed or anything I can do to make it fully converted to 702l?
Please help! thank you so much.
Click to expand...
Click to collapse
First you need to go back to the last 703L 5.1 system (B112) then flash the universal cust mod, then try the dload to B201. You also may have to go back to the last 702L 5.0 rom before you try to update to B201 but i'm not totally sure.

ajsmsg78 said:
First you need to go back to the last 703L 5.1 system (B112) then flash the universal cust mod, then try the dload to B201. You also may have to go back to the last 702L 5.0 rom before you try to update to B201 but i'm not totally sure.
Click to expand...
Click to collapse
thanks.
I downgraded to B112 successfully and then tried the dload update. It didn't even go through the first 5 seconds and failed. I guess it's because my phone's on 703L cust so the 702l stock rom didn't apply to it.
As for downgrading to 5.0, there's still no way of doing that for 702l, so I am still stuck here.
******edited***
I just "fake flashed" back to5.0, which means fastboot flash the required img files, and tried to dload update to B201 of 702l.
It's still not working. Now I am at my wit's end.

iamhcg said:
thanks.
I downgraded to B112 successfully and then tried the dload update. It didn't even go through the first 5 seconds and failed. I guess it's because my phone's on 703L cust so the 702l stock rom didn't apply to it.
As for downgrading to 5.0, there's still no way of doing that for 702l, so I am still stuck here.
******edited***
I just "fake flashed" back to5.0, which means fastboot flash the required img files, and tried to dload update to B201 of 702l.
It's still not working. Now I am at my wit's end.
Click to expand...
Click to collapse
Flash the B112 universal cust in TWRP then fastboot flash back the stock recovery, then try the dload again. If that doesn't work, flash twrp, then the cust mod, then the stock recovery then so a factory reset from settings. If the reset completes successfully then flash twrp again then the cust mod then stock recovery then try the dload method again.

ajsmsg78 said:
Flash the B112 universal cust in TWRP then fastboot flash back the stock recovery, then try the dload again. If that doesn't work, flash twrp, then the cust mod, then the stock recovery then so a factory reset from settings. If the reset completes successfully then flash twrp again then the cust mod then stock recovery then try the dload method again.
Click to expand...
Click to collapse
That's exactly what I did. The dload just wouldn't go beyond 5 seconds.
The problem, I think, is that the universal cust marked the phone as 703l(that's the point of universal cust), but the stock rom B201 is for 702l. Therefore, the first 5 seconds of dloading when it verified the model, the stock rom and the model just didn't match. So the dload failed.
There's no flashable cust for 702l to make the phone match the requirement of stock B201 rom. I think this might be where the problem is.

The cust mod includes the cust from the 701L and 702L as well so it should work as long as you go back to B112. What is the reason you want to go back to the 702L firmware?

ajsmsg78 said:
The cust mod includes the cust from the 701L and 702L as well so it should work as long as you go back to B112. What is the reason you want to go back to the 702L firmware?
Click to expand...
Click to collapse
There are certain functions that only exist in my region, such as the nationwide SMS warning regarding natural disasters. It's a system that being developing in my country. All phone brands will integrate the thing in their roms and push out for OTA. I would like to be on the receiving end. Also, If I need to RMA my phone someday, it will be nice to be able to switch back to stock rom for warranty.
I thought it was easier to switch between models when they were both on the same version of Android. I was wrong.

Hello,
Where can I find the Android 6.0 (B201) for gem-702l ?
Thanks

maskman1 said:
Hello,
Where can I find the Android 6.0 (B201) for gem-702l ?
Thanks
Click to expand...
Click to collapse
http://consumer.huawei.com/tw/tablets/support/downloads/mediapad-x2-tw.htm
Here. But it's for Taiwan gem-702l and it's still a test version, I am not sure if it's applied to other region.
I'll advise you to wait a bit longer for the official version to be out.

Ok, thanks for the input!

Update GEM-701 & GEM-702 To Original B201 & KANGVIP B211

0. TWRP - USB DEBBUG - ADB fastboot
0.a Buy Bootload Code from DC-Unlocker (WORD File) to Dropbox. From original post
1 . Install ADB command line in your windows X
2.a. Download GEM 701L B003 for GEM 701L via ADB
2.b. Download GEM 702L B003 for GEM 702L via ADB
3. Extract with HuaweiUpdateExtractor in UPDATE.APP
these files system.img, cust.img, boot.img, userdata.img, recovery.img.
4. boot into bootloader (Power+VOL down, USB Cable connected) & go to adb command line type ->
fastboot flash system system.img
fastboot flash cust cust.img
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot reboot
5. Your device is clean and Origin ROM From Huawei.
6. Download & put dload in your SDCARD
6.1 dload -> 5GOTO6
- FLASH IT via Updater (from settings Localy) & it should done 100% & go options look and verify build number
6.2 dload -> GEM-702LV100R001C209B005CUSTC158D001
- FLASH IT via Updater (from settings Localy) & it should done 100% & go options look and verify build number
6.3 dload -> X2升级包 for GEM-702LC158B201
- FLASH IT via Updater (from settings Localy) & it should done 100% & BOOTLOOP !!!
6.4 PUT IN YOUR SDCARD -> dload from GEM-702LC158B201
6.4A -> Insert your SDCARD and Reboot and PRESS VOL+ and VOL- at the same time
6.4B-> HUAWEI UPDATE, it should done 100% & go options look and verify build number
6.5-> Your phone is B201 (marsmallow) official and WIFI & Bluetooth is okay !
6.6-> Install TWRP6.0
fastboot flash recovery TWRP-ENG-6.0.img
fastboot reboot
PRESS VOL+ and VOL- at the same time
Download -> [ROM] [6.0] KangVIP Slim B211
Put in your Sdcard & install
Wipe -> Swipe to Factory Reset
Reboot
7. Finish all it's okay :good::good::good::good: on my GEM 701-L & 702-L ps : thank you for your opinions

did anyone tried this method?
Sent from my GEM-701L using XDA-Developers mobile app

Rhonald said:
did anyone tried this method?
Sent from my GEM-701L using XDA-Developers mobile app
Click to expand...
Click to collapse
Nice and clear tutorial with all what is needed to successful update. If you proceed it should work without flaw.

I would Not recomnend that. This way will erase the fitting cust on 701 models. I don't think the cust it's a nice goiter which we can replaced by a randomly selected one. Why do you think the device runs in bootloop on this guide?
This is more complicated than the way AJ figured out.
The 'universal cust 112' is the key.
I did it on 3 devices now with 100% success in dload and no bootloops.
2 factory resets and 3 dloads (106 112 and 209) are necessary.
Then install 202 or 211 KangVIP from AJ to have a full functional rooted ROM with your origin cust you came from.
My device: 701->703 B211 xposed 86

Hi me device is gem 701L convert to 703L B111 nearstock. I installed successfully B211 . after the restart of the Huawei logo on the left . and nothing is happening . i dont understand what's wrong .Finally, I rebooted the fastboot mode.nainstaloval I TWRP and then installs kangvip slim 6 . ok. Only is not working bluetooth and wifi. How do I get it right ? Any Some will not destroy my gem- 701 l ( 703 l )

audioralf said:
I would Not recomnend that. This way will erase the fitting cust on 701 models. I don't think the cust it's a nice goiter which we can replaced by a randomly selected one. Why do you think the device runs in bootloop on this guide?
This is more complicated than the way AJ figured out.
The 'universal cust 112' is the key.
I did it on 3 devices now with 100% success in dload and no bootloops.
2 factory resets and 3 dloads (106 112 and 209) are necessary.
Then install 202 or 211 KangVIP from AJ to have a full functional rooted ROM with your origin cust you came from.
My device: 701->703 B211 xposed 86
Click to expand...
Click to collapse
Perhaps indeed it replaces information of 701, I am not a specialist.
The bootloop when its causes are on both models 701 & 702.
Despite this my tutorial that my 701 & 702 work perfectly with the wifi and bluetooth.
I do not question the quality nor the audioralf skills,
I just shared my tutorial after many trials of other tutorials that never It Works for me.

Well you link files you don't write where you got them from and don't write for wich model they are made for and what are requirements they based on.
Maybe it works, but it's a risk to continue on a bootloop with further installations.
The regular way works without errors.
If someone is looking for another dirty short way :
Simply run the official downgrade script from 6.0 to 5.0. for 702.
It even runs on a 5.0 701 model.
After this it behaves like a 702.
Then you can dload the regular update to 6.0 for 702 models.
After this flash TWRP 6.0 and install AJ b211
This method is also dirty because you loose the 701 cust for your region and hardware
This may be have consequences we don't know.
So better go the regular way AJ had figured out and ask in forum if you habe problems.
My device: 701->703 B211 xposed 86

B111 SimpyGoogle => KANGVIP B211 link?
Hi Audioralf,
thanks for pointing this out. I followed your great guide and got to SimplyGoogle B111 on a GEM-701L. (You updated it with a shortcut to B111, which worked just fine. Some lines in the guide are a bit misleading due to the newer shortcut but all is great).
Now I'd love to get to KANGVIP B211 on Android 6. But how do I get there from B111? I can't find AJs guide you pointed out in your comment. Could be please post a link? (I have searched but without success).

I succeeded
Rhonald said:
did anyone tried this method?
Sent from my GEM-701L using XDA-Developers mobile app
Click to expand...
Click to collapse
I did succeeded with a mixture of both methods.
I started off following the "original version" of AJ and when I never got into upgrading into 6 I decided to stay at Near...B111.
When I saw Oblemay's tuto I decided to try it. Funny enough, coming from B111 I (701l > 703l) I never got the boot loop!
Also, since I was not able to unpack the rar file from step 6.2 I simply ignored this one and continued with 6.3.
Guess what it worked perfectly. Only issue was unstable wifi until I did a factory reset from within 211 (not TWRP)!
I am very happy with my former 701l now on Marshmallow. Thanks to AJ and Oblemay - Maybe it worked for me with Oblemay's (reduced) version as I also live in France .... Do you also have problems with the mail app in 211?

So can anybody provide clear instructions or links which work for 701 on b003? I am really confused right now, because their are so many Different Methods/Versions..

HTML:
Chris0706 said:
So can anybody provide clear instructions or links which work for 701 on b003? I am really confused right now, because their are so many Different Methods/Versions..
Click to expand...
Click to collapse
+1
It could be really good to have some clear way... Actually I was asked about such process by one of russian friends who own GEM701 and do not uderstand nothing, specially using Google translator . As I am owner of GEM703L I am not familiar with 701 ways... But I want to help my companion...

getoliverleon said:
Hi Audioralf,
thanks for pointing this out. I followed your great guide and got to SimplyGoogle B111 on a GEM-701L. (You updated it with a shortcut to B111, which worked just fine. Some lines in the guide are a bit misleading due to the newer shortcut but all is great).
Now I'd love to get to KANGVIP B211 on Android 6. But how do I get there from B111? I can't find AJs guide you pointed out in your comment. Could be please post a link? (I have searched but without success).
Click to expand...
Click to collapse
Do you still need help? I did not see your comment.
The way from 112 to 212 is described many times: Just flash boot, system and recovery from b112. Start system and do a factory reset. Then the update.zip of 211 can be started via firmware update menu. (Select partitionally update)
Then install TWRP and AJ KangVIP 211
My device: 701->703 B211 xposed 86

trurl3 said:
HTML:
+1
It could be really good to have some clear way... Actually I was asked about such process by one of russian friends who own GEM701 and do not uderstand nothing, specially using Google translator . As I am owner of GEM703L I am not familiar with 701 ways... But I want to help my companion...
Click to expand...
Click to collapse
If someone is interested in rooting method of GEM702 with stock B202 ROM. As i wrote one of my koleauges want to root. I was asking in PM @audioralf and @ajsmsg78. Finally using all advices rooting was done successfully by this method (unit should be unlocked and TWRP installed):
1. Copy to root of SD BETA-SuperSU-v2.67-20160121175247.zip
2.Boot to TWRP and before installing SuperSU go to Advanced->Terminal and execute command "echo SYSTEMLESS=true>>/data/.super.su" (without quotes).
3. Not leaving TWRP install SuperSU from SD.
@ajsmsg78 has some comments concerning rooting with systemless supersu:
ajsmsg78 said:
Just flash SuperSU 2.78 in twrp. My roms are already rooted if he wants to go that route but I wouldn't use systemless root on the X2 as it causes app freezing issues. It's something with Huawei's kernel.
Click to expand...
Click to collapse
Now we will see. My companion will testing his installation and report back. if the method proves to be flawless @ajsmsg78 could use it in his ROMs....
EDIT// Unfortunately friend reports so this method gives not fully working root.

Still waiting a clear way to convert GEM-701L B001 to GEM-703L

If you are on b001, try to
flash TWRP always on recovery2 partition:
Fastboot flash recovery2 twrp_eng_5_0.img.
So you can keep the device usb connected.
Then install universal cust mod 112.
Always put update.app file to dload folder on external sd. Always exchange the file within this folder on the next steps.
Start with dload process for B003, if you are on Android 5.0 but boot not on B003.
Start system and select firmware update and press local update to select full update to B003
If you are on b003, then
- flash TWRP eng for 5.0 and install universal cust mod 112
Start in bootloader mode and flash the 015 system, boot and recovery.img
Start system and do reset on EMUI.
Then flash TWRP and install universal cust mod 112 again and start dload with b106 update app
Now start system and repeat reset on EMUI including format internal sd.
Flash TWRP FOR 5.11 and Install again universal cust mod 112 and start dload via EMUI with update.app from b112.
Start system and then start local update with incremental update.zip for 211 in dload folder
Finally install TWRP for 6.0 and install
kangvip 211
My device: 701->703 B211 xposed 86

It fails to update to B003 maybe because of the Region/Vendor.
My Build number is GEM-701LV100R001C199B001

Is it possible to change the Region name or the Vendor?

try if it works, if you install universal cust b112 before b003 dload.
My device: 701->703 B211 xposed 86
---------- Post added at 04:00 PM ---------- Previous post was at 03:05 PM ----------
I have updated the guide in #15
My device: 701->703 B211 xposed 86

Thank you for your time. Will try that later because this is a busy week for me at the office.

Can't flash the TWRP.
Do I have to root first?

[FIXED] Bootloops after flashing TWRP 3.1.0.0 on 2.17.401.2

Hello Guys..
Im HTC One A9, S-OFF. on European Nougat 2.17.401.2..
as you know 2.17.401.2 updates for European versions released barely a week ago, RUU is also available in Collection thread..
i tried official TWRP 3.1.0-0 & unofficial 3.0.3-8 on clean stock European Nougat 2.17.401.2..
TWRP was booting but system was trapped in bootloop i.e. phone was booting again and again..
DID ANYONE SUCCESSFULLY FLASH TWRP ON 2.17.401.2 WITHOUT BOOTLOOPS??
if yes, please let me know the procedure. Thank You
Fixed. Please scroll down and see my post. Thanks @JohnRogers23

Dr.Anshuman said:
Hello Guys..
Im HTC One A9, S-OFF. on European Nougat 2.17.401.2..
as you know 2.17.401.2 updates for European versions released barely a week ago, RUU is also available in Collection thread..
i tried official TWRP 3.1.0-0 & unofficial 3.0.3-8 on clean stock European Nougat 2.17.401.2..
TWRP was booting but system was trapped in bootloop i.e. phone was booting again and again..
DID ANYONE SUCCESSFULLY FLASH TWRP ON 2.17.401.2 WITHOUT BOOTLOOPS??
if yes, please let me know the procedure. Thank You
Click to expand...
Click to collapse
Did you mount system read/write at all? That's what it sounds like to me. You may need to restore a stock system image or flash an RUU, although a factory reset might solve it too.

JohnRogers23 said:
Did you mount system read/write at all? That's what it sounds like to me. You may need to restore a stock system image or flash an RUU, although a factory reset might solve it too.
Click to expand...
Click to collapse
yes i allowed modification to system by TWRP. Should i keep system read only?
Factory reset did not solve the probem.. should i flash system image or boot image again after flashing TWRP ?
will it fix the problem, start my phone normally keeping TWRP?
thank you..

Dr.Anshuman said:
yes i allowed modification to system by TWRP. Should i keep system read only?
Factory reset did not solve the probem.. should i flash system image or boot image again after flashing TWRP ?
will it fix the problem, start my phone normally keeping TWRP?
thank you..
Click to expand...
Click to collapse
Make sure /system is mounted read only until after you've flashed something (for example Magisk or Supersu) that removes dm-verity. If the reset didn't work you'll have to either flash the untouched system image backup or an RUU, no need to mess with the /boot image, and if you only flash the /system image backup it will keep TWRP.

[FIXED] TWRP 3.1.0-0 worked well on 2.17.401.2 :)
1. download TWRP 3.1.0-0 image file from official site.
You will find 2 versions for Hiae , american & European versions, please choose European version, download it.
2. flash twrp via fastboot, then boot into Twrp
3. choose system READ ONLY, dont allow modification by Twrp ( dont wory, twrp still can modify system if zip into system is flashed)
4. now boot into system.. But if you want to flash SuperSU then make a factory reset first then immediately flash latest supersu..

Dr.Anshuman said:
1. download TWRP 3.1.0-0 image file from official site.
You will find 2 versions for Hiae , american & European versions, please choose European version, download it.
2. flash twrp via fastboot, then boot into Twrp
3. choose system READ ONLY, dont allow modification by Twrp ( dont wory, twrp still can modify system if zip into system is flashed)
4. now boot into system.. But if you want to flash SuperSU then make a factory reset first then immediately flash latest supersu..
Click to expand...
Click to collapse
Hello
Hello so I've tried everything unfortunately nothing goes bootloop I have htc one A9 europa version

barbaross said:
Hello
Hello so I've tried everything unfortunately nothing goes bootloop I have htc one A9 europa version
Click to expand...
Click to collapse
TWRP works perfectly on European versions 2.16.xxx.x & 2.17.xxx.x, you just need to remember couple of things..
1. download TWRP 3.1.0-0 European version from official site only.
2. Flash TWRP on a clean stock ROM or Do a factory reset first.
3. Dont allow TWRP to modify system when it asks for first time.
you can try again checking all things mentioned above.

Dr.Anshuman said:
TWRP works perfectly on European versions 2.16.xxx.x & 2.17.xxx.x, you just need to remember couple of things..
1. download TWRP 3.1.0-0 European version from official site only.
2. Flash TWRP on a clean stock ROM or Do a factory reset first.
3. Dont allow TWRP to modify system when it asks for first time.
you can try again checking all things mentioned above.
Click to expand...
Click to collapse
Hello I have tried everything unfortunately can not be a short video of twrp

barbaross said:
Hello I have tried everything unfortunately can not be a short video of twrp
Click to expand...
Click to collapse
Even i got problem after flashing TWRP on OTA updated stock ROM.
What i did is , i downloaded European 2.17.401.2 firmware and RUU.zip from Collection Thread, flashed firmware via Fastboot and flashed Zip using SD card method, then i followed above procedure of flahing TWRP.. all worked fine.. you should try this one..

Dr.Anshuman said:
Even i got problem after flashing TWRP on OTA updated stock ROM.
What i did is , i downloaded European 2.17.401.2 firmware and RUU.zip from Collection Thread, flashed firmware via Fastboot and flashed Zip using SD card method, then i followed above procedure of flahing TWRP.. all worked fine.. you should try this one..
Click to expand...
Click to collapse
I have tried again everything unfortunately it has not worked, someone can upload the right twrp for european version for htc one a9 the official side does not go from twrp, thank you

barbaross said:
I have tried again everything unfortunately it has not worked, someone can upload the right twrp for european version for htc one a9 the official side does not go from twrp, thank you
Click to expand...
Click to collapse
this is download link for official TWRP 3.1.0-0 Hiae European..
https://uploadocean.com/wsuzuczqh0py
please flash this TWRP img file after flashing European 2.17.401.2 Firmware and RUU.zip from collection thread..
https://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344
Best Luck :good:

Dr.Anshuman said:
this is download link for official TWRP 3.1.0-0 Hiae European..
https://uploadocean.com/wsuzuczqh0py
please flash this TWRP img file after flashing European 2.17.401.2 Firmware and RUU.zip from collection thread..
https://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344
Best Luck :good:
Click to expand...
Click to collapse
Hello
Unfortunately it did not work thanks for your help, back android 6.01 is not synonymous
---------- Post added at 07:32 PM ---------- Previous post was at 07:29 PM ----------
Before the stock android 7.0 I could do everything with stock android 6.01 was no problem

barbaross said:
Hello
Unfortunately it did not work thanks for your help, back android 6.01 is not synonymous
---------- Post added at 07:32 PM ---------- Previous post was at 07:29 PM ----------
Before the stock android 7.0 I could do everything with stock android 6.01 was no problem
Click to expand...
Click to collapse
If you are having issue with 2.17.xxx.x then you can try 2.16.xxx.x European
TWRP, SuperSu have no issue with this firmware..
Download it from Collection Thread..

Dr.Anshuman said:
If you are having issue with 2.17.xxx.x then you can try 2.16.xxx.x European
TWRP, SuperSu have no issue with this firmware..
Download it from Collection Thread..
Click to expand...
Click to collapse
I tried with 2.16.xx 2.16.xx can not be insulated

your device encrypted?
Try this:
1. flash and boot to latest official TWRP for A9
2. choose wipe and choose Format Data (it will wipe everything on Internal Memory)
3. type yes and confirm formating data, if you see red text error reboot to Download Mode, reboot to Bootloader and enter TWRP recovery again.
4. repeat step 2
5. wipe cache & dalvik cache
6. reboot to system