To cut it short; let me describe what i've done to my victim RIO-L01
1- I was on RIO-L01B321C185D005 (6.0.1) (Middle East CUST version)
2- I used Firmware Finder application to update to RIO-L01B330C185D005 (OTA, 505 Megabytes) and it was updated successfully.
3- I found another B340C185D005 (OTA, about 167 Megabytes) and i installed it successfully.
4- Next, i thought to do a refresh to my phone by installing B330 again (Full Package, 1.3 GB) but it wasn't successful (i guess because it is a downgrade)
5- I flashed (using fastboot Boot.img, Recovery.img, System.img Successfully) B321C185D005 again and i said let's start from the beginning! And here is when i messed things up.
6- The B340 Updated the CUST version, but when i flashed the B321 didn't update the CUST so now i cannot receive any OTA updates or even use the Stock UPDATE.APP and Stock Recovery to restore any version.
Now, what i need is to restore everything back to it's original state.
Stock ROM (I'll Accept any version )
Stock Recovery
Stock CUST
Here is my current System with ProjectMenu:
Hardware Version: HL1RIOL01M
Bootloader Version: RIO-L01C185B321_APPSBOOT
Kernel Version: RIO-L01C185B321_KERNEL
AP Version: RIO-L01C185B321_SYSTEM
CP Version: RIO-L01C185B340_AMSS
Parameter Version: CVersion: C185, DVersion: D003!
this's my problem too
hope to find solution
kiro_koko said:
this's my problem too
hope to find solution
Click to expand...
Click to collapse
me too
I had the same issue with yours, but a little different.
I've installed C636B320 and forgot to create a backup then I've installed a custom rom and since no backup was created for the stock rom, I cannot go back to it's original state and manually flashing C636B10 works with some hiccups.
Here's what I did.
I went to the bootloader/fastboot section of the device and erased my system, recovery, boot, and userdata partitions and took my phone to a service center. I got my board replaced for free since it's under warranty.
Board replacement is only applicable if they will not be able to revive your phone by reinstalling any stock rom that they have. Don't worry they will not find out that you've unlocked your bootloader since they cannot access it via Volume Down+Power Key, it's not working for MM roms.
It sounds like a big hasssle, but it works!
Unfortunately, I've completed my warranty period. This means that i'll pay a lot to change the board. I think I only have 2 last hopes... First, is to get a new official update, which will be a higher version of the current CUST. Second, is to get an image of a similar phone with original cust and replace mine..
mooooorz1981 said:
To cut it short; let me describe what i've done to my victim RIO-L01
1- I was on RIO-L01B321C185D005 (6.0.1) (Middle East CUST version)
2- I used Firmware Finder application to update to RIO-L01B330C185D005 (OTA, 505 Megabytes) and it was updated successfully.
3- I found another B340C185D005 (OTA, about 167 Megabytes) and i installed it successfully.
4- Next, i thought to do a refresh to my phone by installing B330 again (Full Package, 1.3 GB) but it wasn't successful (i guess because it is a downgrade)
5- I flashed (using fastboot Boot.img, Recovery.img, System.img Successfully) B321C185D005 again and i said let's start from the beginning! And here is when i messed things up.
6- The B340 Updated the CUST version, but when i flashed the B321 didn't update the CUST so now i cannot receive any OTA updates or even use the Stock UPDATE.APP and Stock Recovery to restore any version.
Now, what i need is to restore everything back to it's original state.
Stock ROM (I'll Accept any version )
Stock Recovery
Stock CUST
Here is my current System with ProjectMenu:
Hardware Version: HL1RIOL01M
Bootloader Version: RIO-L01C185B321_APPSBOOT
Kernel Version: RIO-L01C185B321_KERNEL
AP Version: RIO-L01C185B321_SYSTEM
CP Version: RIO-L01C185B340_AMSS
Parameter Version: CVersion: C185, DVersion: D003!
Click to expand...
Click to collapse
Absolutely the same situation, same scenario, same versions as a result.
Have you finally solved this issue?
odemwingie said:
Absolutely the same situation, same scenario, same versions as a result.
Have you finally solved this issue?
Click to expand...
Click to collapse
No Still stuck in this version
anyone developer can help me ? i dont know what to do now icant use my phone
When Oreo edition will be released for our phone?
Related
Hello, friends!
It's been a really long time after my Q900 and X3D-SE...
For those who are having trouble with Asus Fonepad 7 2014 FE170CG in terms of softbrick, kindly take some time to read this thread.
I am currently on Latest Kitkat with version: 11.2.3.33
1.) In terms of Rooting(Offcourse YES, this tab is rootable) i rooted this device with Rootzenphone.apk(attached below). Kindly follow the tutorial here to root the device. When it doesn't get rooted in first time, repeat it. I got it rooted at 1st time itself. After rooting, i removed all the apps i don't need!
2.) To update your Fonepad, download the appropriate zip firmware(zip rom) from the Asus site. Download the matching SKU's only. For eg: WW-WW, CN-CN, JP-JP etc... And i really don't know about installing CN firmware over WW variants. After downloading, rename your file accordingly. Eg: UL-K012-WW-11.2.3.33-user.zip to k012_sdupdate.zip and put the file in the root of external SD card. Time to backup all your critical data! Finally switch off your tab. Now press Vol up + Power buttons until you see the Asus logo. If you are in Jelly Bean, the options are slightly different where you have to choose SD update. Your tab will now reboot to recovery, installs the update and reboots back to the installed firmware. On the other hand, if you are in KitKat, the options like SD download and SD update won't be available because they are removed from the newer Fastboot images. The SD update and SD download are now replaced by recovery option which is the one you need to select. After that device will reboot and install the updates.
3.) To downgrade the firmware to JellyBean, download the appropriate version of the firmware file(I used UpdateLauncher_K012_WW_10_32_1_33_1.zip) and follow the steps as above. Your device will be downgraded. In this version the options on the Droidboot menu will be different from the KitKat version. Just choose SD update to install any other updates.
4.) This is the main part for which i am creating this thread!
THE SOFT BRICK
I was pulling off my hairs for about a day trying to figure out the problem.
Reason for my softbrick: I got a feeling that my device was slightly going slow and the amount of available free RAM was only 200MB. SO, i was considering to Downgrade the firmware from Kitkat to Jellybean. I downloaded the Jellybean firmware UpdateLauncher_K012_WW_10_32_1_33_1.zip from the Asus site and installed it using the method above! Everything went fine and device booted to JellyBean with the familiar interface. Everything was fine but i noticed that the device was slightly heating up and was missing many features like dual apps etc... Hence i decided to go back to KitKat which is were all the problems began! I downloaded the latest firmware UL-K012-WW-11.2.3.33-user.zip. Installation begun as usual but at the end, installation was terminated with a message error. I was shocked! When i rebooted the device i got a USB icon with a red progress bar in a second and went away! The device neither booted nor charged! I repeatedly tried this procedure but failed continuously. I booted to the Droid Boot and saw the firmware version was fine and can't figure what the problem was! But i noticed that the same JellyBean firmware installed again without any glitches and booted fine. When i tried the Kitkat firmware, it failed again and device didnt't boot. This is tricky part! So, i downloaded the first kitkat firmware UL-K012-WW-11.2.3.18.2-user.zip after the JellyBean and tried to install it. To my suprise, the installation went fine and device booted up with that KitKat firmware. Now i put the latest Kitkat firmware UL-K012-WW-11.2.3.33-user.zip to the external SD card and tried to install it and it successfully installed :victory: :victory: Now i am back on the latest firmware
My recommendation : If you do anything, make sure to backup data and have knowledge on what you are doing. Thanks for reading this thread. Please press thanks if i helped you!
Lollipop update has been released some time ago. Please remember to unroot before you update or else you'll get soft bricked.
downgrade and ota update
In lillipop i got major laggs and baterry drained more than 50% over night in standby mode.
So I downgrade to latest kitkat WW_V11.2.3.33 from asus site, using fastboot and intel temporary cwm recovery.
It works great but now ifwi is 64.33 from lollipop, not 64.25 from kitkat.
It seems there is an OTA update WW_V11.2.3.34 but I dont get notification for download.
Is there any way to downgrade ifwi version?
Or do I have to ask here someone for capture the WW_V11.2.3.34 OTA update from /cache and upload here?
Or is there any fix for lillipop horrible lag (2-3 secs after presing or swiping) and masive battery drain? I tried factory reset lollipop and even reinstall with fastboot erase system and intel thetered temp cwm install UL-K012-WW-12.8.1.26-user.zip
b0by said:
In lillipop i got major laggs and baterry drained more than 50% over night in standby mode.
So I downgrade to latest kitkat WW_V11.2.3.33 from asus site, using fastboot and intel temporary cwm recovery.
It works great but now ifwi is 64.33 from lollipop, not 64.25 from kitkat.
It seems there is an OTA update WW_V11.2.3.34 but I dont get notification for download.
Is there any way to downgrade ifwi version?
Or do I have to ask here someone for capture the WW_V11.2.3.34 OTA update from /cache and upload here?
Or is there any fix for lillipop horrible lag (2-3 secs after presing or swiping) and masive battery drain? I tried factory reset lollipop and even reinstall with fastboot erase system and intel thetered temp cwm install UL-K012-WW-12.8.1.26-user.zip
Click to expand...
Click to collapse
For some reasons, i too didn't get that update! I am also in 11.2.3.33 I flashed the device 4 times just to get this update but didn't!
b0by said:
In lillipop i got major laggs and baterry drained more than 50% over night in standby mode.
So I downgrade to latest kitkat WW_V11.2.3.33 from asus site, using fastboot and intel temporary cwm recovery.
It works great but now ifwi is 64.33 from lollipop, not 64.25 from kitkat.
It seems there is an OTA update WW_V11.2.3.34 but I dont get notification for download.
Is there any way to downgrade ifwi version?
Or do I have to ask here someone for capture the WW_V11.2.3.34 OTA update from /cache and upload here?
Or is there any fix for lillipop horrible lag (2-3 secs after presing or swiping) and masive battery drain? I tried factory reset lollipop and even reinstall with fastboot erase system and intel thetered temp cwm install UL-K012-WW-12.8.1.26-user.zip
Click to expand...
Click to collapse
Hello! Ifwi is easy! Take the KitKat Firmware and unzip it complitely, so that you have acces to the files of the rom.zip (Firmware)! In the Firmware (1st-Site) is a ifwi.zip! Unzip this ifwi.zip, and take the dnx_fwr.bin (VLC) and the ifwi.bin (VLC) file, and copy it to your adb/fastboot binarys! Then go to fastboot-mode and First: fastboot flash dnx dnx_fwr.bin, when its done, Second: fastboot flash ifwi ifwi.bin, when its done, reboot bootloader, and check ifwi-version! Should be the version you have flashed!
But do it in your own! Im not responsebile for failure or brick!
Bluetooth permission to receive apk
hi
i cant underestand English very well but i have question
i have asus fonepad 7 fe 170 cg kitkat and i rooted this but i cant receive .apk with Bluetooth for this reason i installed xposed and i downloaded Bluetooth ToolKit.apk
whit this program my bluetooth have permission to receive apk but i want to know what file chenged in root divice and in permission that my bluetooth can receive apk
please say me what file chenged???????
Are you getting play store links when you send an .apk file or can't receive files at all??? And i never installed xposed since it has no use for me....
roselanguste said:
Hello! Ifwi is easy! Take the KitKat Firmware and unzip it complitely, so that you have acces to the files of the rom.zip (Firmware)! In the Firmware (1st-Site) is a ifwi.zip! Unzip this ifwi.zip, and take the dnx_fwr.bin (VLC) and the ifwi.bin (VLC) file, and copy it to your adb/fastboot binarys! Then go to fastboot-mode and First: fastboot flash dnx dnx_fwr.bin, when its done, Second: fastboot flash ifwi ifwi.bin, when its done, reboot bootloader, and check ifwi-version! Should be the version you have flashed!
But do it in your own! Im not responsebile for failure or brick!
Click to expand...
Click to collapse
I have 4 .bin files in ifwi.zip:
CLVp_CSAX_FWR_DnX_20.3E.bin
CLVp_CSAX_OS_DnX_20.3E.bin
IFWI_v64.25_CSAX_PROD.bin
signed_CLVP_CSAX_SoftFuseFile.bin
Dont I have to flash them all? or just the ...FWR_DnX.bin and IFWI_v64.24....bin?
My dear friends, please concentrate on getting Clockworkmod and Cyanogenmod... I am trying real hard here. I contacted all the devs i could, none willing to help me! No device & vendor tree, Locked bootloader, No custom recovery, No stable ROM...... Really feeling so down
OK! You have Four ifwi-Files, Yes then Flash them All!
Expecting some help over here!!! Support me for creating device and vendor trees........
Downgrade IFWI version!
roselanguste said:
Hello! Ifwi is easy! Take the KitKat Firmware and unzip it complitely, so that you have acces to the files of the rom.zip (Firmware)! In the Firmware (1st-Site) is a ifwi.zip! Unzip this ifwi.zip, and take the dnx_fwr.bin (VLC) and the ifwi.bin (VLC) file, and copy it to your adb/fastboot binarys! Then go to fastboot-mode and First: fastboot flash dnx dnx_fwr.bin, when its done, Second: fastboot flash ifwi ifwi.bin, when its done, reboot bootloader, and check ifwi-version! Should be the version you have flashed!
But do it in your own! Im not responsebile for failure or brick!
Click to expand...
Click to collapse
Hello, i tried to downgrade IFWI version by following your method... Everything flashed successfully but the version number stays the same! For eg. if i flash version 64.25, it still stays the 64.33 version of Lollipop firmware only!!! Do you know why???
irfanjunaid said:
Hello, i tried to downgrade IFWI version by following your method... Everything flashed successfully but the version number stays the same! For eg. if i flash version 64.25, it still stays the 64.33 version of Lollipop firmware only!!! Do you know why???
Click to expand...
Click to collapse
Hello! Have you more than this two files in your ifwi.zip? In many cases there are more files in ifwi.zip! Unzip the ifwi.zip and flash all files what is in there! Token.files=fastboot flash token filename, dnx.files=fastboot flash dnx filename, and ifwi.files=fastboot flash ifwi filename! But i suggest you, when you not need this ifwi/dnx for anything, then you should stay on the newer ifwi?! ifwi is BIOS for Intel Phones! So you have KitKat with the newer BIOS-update from Lollipop! Its like a BIOS-update for PC!
Ever since i flashed that Lollipop 64.33 IFWI, i didn't get access to the 11.2.3.34 update at all! So, do you think this IFWI version is problem or Asus pulled that firmware from its servers???
@irfanjunaid , Hello sir.
I just got Asus model: k012 Stuck on logo.
Now i am downloading all the firmwares u mentioned in the OP, but one question .. Did u flash them via stock recovery or u flashed the temporary cwm recovery available .
Sobaro said:
@irfanjunaid , Hello sir.
I just got Asus model: k012 Stuck on logo.
Now i am downloading all the firmwares u mentioned in the OP, but one question .. Did u flash them via stock recovery or u flashed the temporary cwm recovery available .
Click to expand...
Click to collapse
Always flash Stock ROM via stock recovery.... I did via stock recovery... But don't forget, rename the downloaded zip file to k012_sdupdate.zip and put it into a clean formatted SD card. Now press volume up + Power button until you see Asus logo. Now choose Recovery. Now your tab boots to recovery, installs firmware and reboots itself.... Note: No downgrade possible, cannot change SKU(WW-CN etc.....)
I get stuck at the Asus Logo after intel splash.... with a spinning wheel that keeps on going and going and going.... I have download the files you mentioned above, put them on SD card but cannot boot into droidboot, it goes back to main screen. When I select Recovery, it runs about 5 seconds and gives error and then restarts. What seems to be the problem here?
Thanks!
Jabbacks said:
I get stuck at the Asus Logo after intel splash.... with a spinning wheel that keeps on going and going and going.... I have download the files you mentioned above, put them on SD card but cannot boot into droidboot, it goes back to main screen. When I select Recovery, it runs about 5 seconds and gives error and then restarts. What seems to be the problem here?
Thanks!
Click to expand...
Click to collapse
What version of firmware are you in now? Is it rooted? Did you try a factory reset? After factory reset allow tab to take some time to boot up... After that go developer settings -> turn ON usb debugging... Now in PC, run adb via commandline and run adb reboot bootloader... Now see if it goes to droidboot...
This is what I find in bootloader mode. Why can't it go in to droidboot?
IFWI Version: 64.25
SERIAL: E60KBC383526
DROIDBOOT VERSION: TW_FONEPAD-11.2.3.18.2-20141022
PRODUCT: K012
Following Firmwares:
UL-K012-WW-11.2.3.18.2-user.zip
UL-K012-WW-11.2.3.33-user.zip
I tried the old version but to no avail. Also the latest!
Thanks!
Jabbacks said:
This is what I find in bootloader mode. Why can't it go in to droidboot?
IFWI Version: 64.25
SERIAL: E60KBC383526
DROIDBOOT VERSION: TW_FONEPAD-11.2.3.18.2-20141022
PRODUCT: K012
Following Firmwares:
UL-K012-WW-11.2.3.18.2-user.zip
UL-K012-WW-11.2.3.33-user.zip
I tried the old version but to no avail. Also the latest!
Thanks!
Click to expand...
Click to collapse
This is the droidboot.... You can now connect your tab to PC and issue fastboot commands to it.... For example: Fastboot erase cache
But for heaven's sake please don't install lollipop update.....
Now try this: Fastboot erase cache
Fastboot erase userdata
Now choose reboot....
See if it boots up....
Hi,
I am running CYanogenMod 13.0-20360525 UNOFFICIAL tritevzw
Baseband N910VVRU2CPJ2
Build Number: ANdroid 6.0.1 MOB30JN910VVRU2BPA1
Whenever I go into settings and click on "Security" I get a popup box that says"
"Unfortunately Settings has stopped"
To try to fix this I have gone into recovery and wiped dalvik and caches.
Thanks for any help!
plainbum said:
Hi,
I am running CYanogenMod 13.0-20360525 UNOFFICIAL tritevzw
Baseband N910VVRU2CPJ2
Build Number: ANdroid 6.0.1 MOB30JN910VVRU2BPA1
Whenever I go into settings and click on "Security" I get a popup box that says"
"Unfortunately Settings has stopped"
To try to fix this I have gone into recovery and wiped dalvik and caches.
Thanks for any help!
Click to expand...
Click to collapse
What build of CM13 did you flash? Your build number says BPA1, but it should be saying CPF3.
quinciebee said:
What build of CM13 did you flash? Your build number says BPA1, but it should be saying CPF3.
Click to expand...
Click to collapse
Hi quinciebee, thanks fo ryour reply.
I was on ANdroid 6.0.1 MOB30JN910VVRU2 BPA1 and firmware BPA1
Then I wanted to try out Hsbadr's new 7.1.1 Nougat Rom and it required new CPJ2 firmware so I odin'd it in.
I TWRP backed up my ANdroid 6.0.1 MOB30JN910VVRU2 BPA1 build I have been running for months.
Then flashed his newest "EmotionOS" But could not get 4G LTE to work so I restored my 6.0 backup since I cant function on 3G only and no one in these forums was able to help me.
Hope that wasn't too confusing
Oh by the way, I am doing this on a Developer Edition Note 4 on Verizon
When I flashed CPJ2 firmware I used a partial build as explained here:
https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
He quotes:
Quote:
"If you're already on unlocked Android 6.0.1 Marshmallow bootloader, you can extract and flash the DevEd partial fimware via Odin to upgrade:
N910VVRU2CPJ2_PartialFirmware_DevEd.tar.md5.7z
This will upgrade the base firmware (NON-HLOS, modem, rpm, sbl1, sdi, and tz) to N910VVRU2CPJ2."
plainbum said:
Hi quinciebee, thanks fo ryour reply.
I was on ANdroid 6.0.1 MOB30JN910VVRU2 BPA1 and firmware BPA1
Then I wanted to try out Hsbadr's new 7.1.1 Nougat Rom and it required new CPJ2 firmware so I odin'd it in.
I TWRP backed up my ANdroid 6.0.1 MOB30JN910VVRU2 BPA1 build I have been running for months.
Then flashed his newest "EmotionOS" But could not get 4G LTE to work so I restored my 6.0 backup since I cant function on 3G only and no one in these forums was able to help me.
Hope that wasn't too confusing
Oh by the way, I am doing this on a Developer Edition Note 4 on Verizon
When I flashed CPJ2 firmware I used a partial build as explained here:
https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
He quotes:
Quote:
"If you're already on unlocked Android 6.0.1 Marshmallow bootloader, you can extract and flash the DevEd partial fimware via Odin to upgrade:
N910VVRU2CPJ2_PartialFirmware_DevEd.tar.md5.7z
This will upgrade the base firmware (NON-HLOS, modem, rpm, sbl1, sdi, and tz) to N910VVRU2CPJ2."
Click to expand...
Click to collapse
How did you flash CM13, and did you flash the 09/19 build?
quinciebee said:
How did you flash CM13, and did you flash the 09/19 build?
Click to expand...
Click to collapse
The build date is May 25 2016
Here is a list of roms of that ilk
https://forum.xda-developers.com/devdb/project/?id=12650#downloads
plainbum said:
The build date is May 25 2016
Here is a list of roms of that ilk
https://forum.xda-developers.com/devdb/project/?id=12650#downloads
Click to expand...
Click to collapse
Then I think that's the problem, you'll have to clean flash the 09/19 build.
Delete
quinciebee said:
Then I think that's the problem, you'll have to clean flash the 09/19 build.
Click to expand...
Click to collapse
I flashed to 09/19 build the phone would not boot. I kept getting a rapid glow behind the Blue android mascot.
I then tried to odin the BOG5 firmware and I got errors . rebooted the phone and it wouldnt boot.
Now just bootloops to the samsung screen,
It's borked.
I think I lost Dev Edition and the best I can do is start from scratch?
Not sure where to go now.
plainbum said:
I flashed to 09/19 build the phone would not boot. I kept getting a rapid glow behind the Blue android mascot.
I then tried to odin the BOG5 firmware and I got errors . rebooted the phone and it wouldnt boot.
Now just bootloops to the samsung screen,
It's borked.
I think I lost Dev Edition and the best I can do is start from scratch?
Not sure where to go now.
Click to expand...
Click to collapse
Is the BOG5 firmware stock? If so, you shouldn't have flashed it. If you still have TWRP and root, take these steps to clean flash to CM13.
1. Boot to TWRP, wipe all but your External Storage (SD Card)
2. Flash CM13 09/19 zip
3. Flash the boot image from CM13 07/24
(Click on install image, select the boot.img file, you will then see two choices: boot and recovery, select boot only, then swipe to flash.)
4. Flash gapps and SuperSU zip
5. Reboot
The rapid blinking was happening because you need the boot image from 07/24 in order for the rom to load properly. I'd post the boot image for you, but it exceeds the file size limit. To get the boot image, download the CM13 07/24 build, unzip the file, and extract the boot.img file to your SD card, along with everything else that you want to flash. Let me know if you need me to provide more details on any of the steps.
I can't even get into twrp.
All I can do is get into "Download mode"
I have started a new thread looking for help here:
https://forum.xda-developers.com/no...p-screwed-vzw-dev-ed-software-update-t3530282
plainbum said:
I can't even get into twrp.
All I can do is get into "Download mode"
I have started a new thread looking for help here:
https://forum.xda-developers.com/no...p-screwed-vzw-dev-ed-software-update-t3530282
Click to expand...
Click to collapse
What do you see when you try to boot into recovery?
Hi quinciebee,
I posted this before I borked my phone, before you started helping me.
How I got here was I was trying to upgrade the firmware so I could them flash The ne 7.1.1 "EmotionOS"
I was following the instruction here:
https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
Specifically where is says:
"If you're already on unlocked Android 6.0.1 Marshmallow bootloader, you can extract and flash the DevEd partial fimware via Odin to upgrade:
N910VVRU2CPJ2_PartialFirmware_DevEd.tar.md5.7z
This will upgrade the base firmware (NON-HLOS, modem, rpm, sbl1, sdi, and tz) to N910VVRU2CPJ2."
It flashed fine and then I installed the EmotionOS and all went well but I could NOT get 4G LTE to work, only 3G.
So I abandoned it and reflashed a backup of the CM 13 I was running since May 25.
I was good on cm13 but I got errors when I was in settings and tried to go into "Security"
Im all god now and I will be trying to get back to 6.0 and then 7.1.1 after my house guests leave.
The phone is running fine in 5.1.1.
THanks again!
My phone was routed and i tried to install the last update from huawei then it stuck in the recovery mod sp i had to install an unofficial cm13 and now i want to return to huawei official system rui 4.01 what should i do ?
Return to official
Simpro said:
My phone was routed and i tried to install the last update from huawei then it stuck in the recovery mod sp i had to install an unofficial cm13 and now i want to return to huawei official system rui 4.01 what should i do ?
Click to expand...
Click to collapse
If you already downloaded official firmware for your model, put it on root folder on your sdcard or internal memory, in folder named "dload" (without quotes). It should contain two files: recovery.img and UPDATE.APP. Then turn off your phone, and turn it on with holding Power+Volume Up+Volume Down. Wait for install to finish, it will reboot itself when done. You will lose all your data on internal storage and root, so you will need to install TWRP and SuperSU again if needed.
What if it stuck again in twrp like the first time ?
Simpro said:
What if it stuck again in twrp like the first time ?
Click to expand...
Click to collapse
Recovery.img in dload folder will replace TWRP with default Huawei recovery. Also, i was stucked in earlier TWRP recovery, with version 3.0.2-0 it was ok.
If you don`t have need for root, rom will work with default recovery.
Ok thank you i will try it
Where i can find a stock firmware for gx8 (i'am from morocco)
Simpro said:
Where i can find a stock firmware for gx8 (i'am from morocco)
Click to expand...
Click to collapse
Hm, not sure, regional Huawei website for Morocco doesn't list GX8, you could try with rom from this forum: https://forum.xda-developers.com/gx8/how-to/g8-g7-plus-official-roms-europe-t3294362 .
it will be in middle east like my device
http://consumer.huawei.com/kw-en/support/products/downloads/detail/huawei-g8-kwen.htm?id=84325
Hello Everyone
I have a Xa1 Ultra phone (G3223)
After 3 full days of searching how can i root my phone i have come to the conclusión that is not posible because of these failed attemps :
1.- My firmware stock versión (working property) its 48.1.A.2.109 i couldnt find any custom kernel nor recovery that Works with this firmware and because of that i cant flash it, so i cant root it.
2.- I could not find and older versión of firmware that had a custom boot.img or recovery.img so i could not downgrade my phone to root it.
3.-There's only 1 post i found on this forum that had a working custom kernel and recovery to be able to root a xa1 ultra Xperia, but his stock firmware versión was 48.1.A.2.50 so as it does not matched mine any attemp to flash it got me a bootloop
So in resume is there anyway i could rot my xa1 ultra phone or all of my assumptions on my researchs are correct?
my stock firmware is G3223_48.1.A.2.109 is there any way i can root it?
Thanks in advance for any information about the subject
The furthest I got is to the conclusion that we need to downgrade to firmware G3223_48.1.A.2.101, there's a working magisk install for that.
I can't get the firmware anywhere and this forum is basically a cemetery.
Mighty_Rearranger said:
The furthest I got is to the conclusion that we need to downgrade to firmware G3223_48.1.A.2.101, there's a working magisk install for that.
I can't get the firmware anywhere and this forum is basically a cemetery.
Click to expand...
Click to collapse
Haven't tested but I found this >> G3223_48.1.A.2.101 https://drive.google.com/file/d/1-oCN7am9nL5TiDQs5uUdLGtW2zEoSVpq/view
It was listed midway through this website >>> https://www.martview-forum.com/thre...-version-firmware-ftf-lock-remove-file.23366/
The .101 downgrade went fine with flashtool, but the TWRP package I found on the janjan thread just boot loops. In fact, anything that I try ends in bootlooping, even fastboot booting an extracted kernel without modification (extracted with either AIK or flashtool).
I think this phone will be impossible to root unless we find the original 48.1.A.2.50 software.
Mighty_Rearranger said:
The .101 downgrade went fine with flashtool, but the TWRP package I found on the janjan thread just boot loops. In fact, anything that I try ends in bootlooping, even fastboot booting an extracted kernel without modification (extracted with either AIK or flashtool).
I think this phone will be impossible to root unless we find the original 48.1.A.2.50 software.
Click to expand...
Click to collapse
After flashing TWRP did you immediately factory reset? [Flash TWRP, reboot into TWRP, Wipe]. With other devices I've had issues occur if I did not remember to.
[GUIDE] Back to stock ROM howto / Downgrade howto
There maybe a number of reasons to go back to the stock ROM. We do not discuss them here :) But what to do if you flashed something, wanting to go back to stock, and did not brick your Realme X2 yet? :) Here is super quick howto guide. There are...
forum.xda-developers.com
this guys says
I have found out that in fact stock recovery does not exist as a prebuilt file It is being created by the script /system/bin/install-recovery.sh on a basis of stock boot partition and a patch file /system/recovery-from-boot.p
It means in theory you can recreate stock recovery having only Realme ozip file.
EDIT1 The command to do it in Linux shell is
Code:
bspatch boot.img selfmade_stock_recovery.img recovery-from-boot.p
Cool! Tested.
EDIT2. For the current moment when unlocked bootloader breaks fingerprint sensor: as soon as the bootloader is locked again, fingerprint starts functioning as it should.
EDIT3 Becomes clear that each ROM release has its own stock recovery which is generated automatically on the basis of boot.img and recovery-from-boot.p . Not only boot.img is being changed each release, but recovery-from-boot.p is changing as well. If the wrong stock recovery is installed, you might not be able to decrypt data and connect to WiFi from within recovery. Seemingly it may bring you serious problems if locking back bootloader (thus bricking the device). Good thing (as I understood, but not checked yet) is that after flashing stock ROM with a help of a stock recovery next reboot should replace your stock recovery with an up-to-date version of it. So to be on a safe side make sure that you rebooted to system and that your recovery reflashed by the system before you lock bootloader.
EDIT4 In order to combine everything in one place:
Stock recoveries for RMX1991 (China version): here
Stock recoveries for RMX1992 (India version): here
Stock recoveries for RMX1993 (Euro version): here
EDIT5 In later ROM releases patch and script files are relocated into vendor partition, they are /bin/oppo-install-recovery.sh and /recovery-from-boot.p there.
EDIT6 Please note that the method above is working with officially downloaded ROMs from realme support site (read here why).
any idea how to explain this in easy understanding word for me to have a stock recovery.img for RMX3363