Develop Bugs

Problems updating to 2.29.405.2

Hello all,
I tried to update to 2.29.405.2.
My Desire is rooted with 2.10.405.2 ROM (the original one).
I downloaded the update by manually checking for an update(via Wifi), ran it, and when the mobile rebooted I got this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I clicked the power button and got the recovery menu and beneath that it said:
Code:
ClockworkMod Recovery v.2.5.0.7
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify the whole-file signature
E:signature verification failed
Installation aborted.
What should I do?
PS: This is the first update I am installing..I 'm new to anroid systems.
Thank you for your time!

If you update a rooted ROM there is a good chance you will end up with problems such as boot loop.
Signature verification failed because you are trying to apply an update to a modified ROM. You can turn it off and apply it but it's not recommended as said already.

Then what should I do?

pspuser007 said:
Then what should I do?
Click to expand...
Click to collapse
Update using Gold Card, but first use search button

or...
just get the RUU from shipped roms and run that...

First you would not lose much from not updating to 2.29, the only thing that is worth it is for the new radio, but if you are okay now, I don't think there is any reason to update.
If you want to do it, nevertheless, you should first unroot.
If your original ROM was 2.10.405.2 ,in other words, if you are not branded then you would not need to use a goldcard.

I just read you reply, 3722.
Well, I am thinking about it because of these:
http://forum.xda-developers.com/showpost.php?p=9808553&postcount=15
What should I do?
*Thank you all for the replies!

First tell us whether you are branded.
If you are you couldn't flash 2.10.405.2 version without a goldcard, and you said that you are on that version with root.
So either you have already made a goldcard or you are not branded.

i think 2.10.405.2 is an unbranded WWE rom.
the link to download 2.29.405.2 is below:
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_151783_signed.exe
all you need to do is download this and after you've put your phone into fastbootand connected it to your PC , run the .exe.
this will get you to 2.29.405.2 but your phone will be unrooted and wiped so your contacts / apps etc. should be backed up.
you can then root again if needed.
HTH

just confirmation - 2.10.405.2 is unbranded

I am unbranded because I haven't used a goldcard to root my desire.
I 've downloaded the RUU.
Ran it, and when I got the screen that informs me about the progress and at the phone I got a black screen with silver HTC letters.
The RUU progress bar windows closed and gave me a message about checking that the phone is connected to the USB.
I disconnected the USB and saw the fastboot screen with only option RUU.
Plugged the usb cord again, and got the black screen with silver HTC letters.
Nothing happened.
So I closed the RUU.
Now what should I do with the device?
Turn off by removing the battery?

ok, can you put your phone into fastboot while not connected to the PC (back & power). you should see fastboot in a red box.
then connect to the PC, this should now change to fastboot USB.
if this is the case, try running the RUU at this point.
oh, and try not to be too hasty unplugging or taking the battery out

I just ran the RUU again and it's upgrading now.
Will reply, If I get any problems!
Thanks a lot mikep and all the other members that replied!

no problem, it will probs take approx 10 mins.
i hope you've got your contacts/apps backed up?
if you've used titanium, you will have to root again to gain access to them (Unrevoked).
hope it goes well - let us know

It went smoothly
I 've backed up with Titanium.
I have to re-root.
Will do it after I return home (in 3 hours).
Will reply here if anything occurs!
Thanks a lot again!

Happy Days!!!

Everything OK! I rooted & restored the backup.

Good stuff! Make sure you make another nand backup now you're on the newer rom so you have one to fall back to
Sent from my HTC Desire using XDA App

When you say another nand backup?
What is this "nand backup"? :-S (sorry I don't know much)
You mean backing up my whole system+data so that I can restore them if I try a custom ROM that I don't like?

Yep, correct.
Make a backup thru the clockworkmod recovery or thru rom manager.
You will then always be able to get back to the position you're at now.
Hope this makes sense
Sent from my HTC Desire using XDA App

incredible 2 / revone freeze

Hi all, love this forum, much much much to learn from this place
Ok, long story short, rooted dinc 2 from htcdev, following steps from this guy but got no further then that cuz the s-on...
read around and found a few guides to s-off if I had hboot-0.97.0000 ... problem was I had hboot-0.98.0000, so I found XDA.... yeah
I then followed the steps outlined here to drop back to hboot-0.97.0000 even if I had custom roms etc installed (outlined in the (HSO) section on post #2).
Success, downgraded per the tutorial.
So here is what changed:
downgraded to 0.97.0000 from 0.98.0000
radio went from 1.09.01.0312 to 1.09.01.0622
kernel went from 2.6.35.9-g11de853 to kernel 2.6.35.9-g6760582
[email protected] #1 remained un changed
baseband went from 20.32w.30.0813u_1.09.01.0312 to 20.27w.30.0811u_1.09.01.0622
build# went from 6.04.605.07 cl353602 release-keys to 2.18.605.3 cl79787 release-keys
android vs. went from 2.3.4 to 2.3.3
So next I re tried the steps here for s-off, but every time my phone just freezes, locked up tight, no buttons do anything, this happens at step #4. if it sits for like 15 minutes it eventually reboots itself, otherwise removing the battery is the only option.
Am I missing something, I am new to rooting, so it is very possible, lol

ok, so I read and read until I worked out the s-off issue, I am now s-off
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
now my big problem is No Service.
I searched XDA and Google for the resolution and found the answer is supposed to be the radio img, so I found several img's here.
Since my radio prior to all this was 1.09.01.0312, I chose the one labeled 6.01.605.05 OTA: 1.09.01.0312...
I loaded the file onto my sd after renaming it to PG32IMG.zip, rebooted phone, let it update, reboot the phone, then pulled battery, booted into Clockwork so I could remove the PG32IMG.zip file via usb mount. rebooted completely, still No Service.
Current info after completing Revolution/S-off:
hboot-6.133.1002
radio: 1.09.01.0312
kernel: 2.6.35.9-g6760582
[email protected] #1
baseband: 20.32w.30.0813u_1.09.01.0312
build# 2.18.605.3 cl79787 release-keys
android vs. 2.3.3
Any suggestions on where I should go from here, anyone?

Load a rom of your choosing and activate the phone

Ok, so, I assume I can load, say Cyanogen's 7.2.0 zip file onto my sd card, boot hboot, select recovery to get into clockworks menu & then simply install zip rom sd card?

Just not having the best of luck, modding, lol
Downloaded Cyanogenmod 10.1, placed on sd, installed zip via clockwork mod, rebooted and now I am stuck in a boot loop here, at the Cyanogen animated boot screen, learning a lot, really fast, lol

So I tried and tried installing different mods and even completely re following tutorials from the beginning to resolve my issue with "No Service" after installing the Cyanogenmod 10.1, to get the Radio working. No matter what I tried, no success.
I even called a friend in Florida who works high up in management for another provider, who had me log into the phone and dial ##778 and then check some NAM settings. Even doing this didn't resolve my issues.
Just after I hang up the phone with him, I find a post here for Cyanogenmod 10.1 Borked Radios. Will be trying this after I read and read the post to make sure I follow it to a tee so I do not waste another 20 + hrs walking in circles.
Posts:
First post, Second post, Third post... So then I find this post that says Post 2 - Restoring a non-functioning radio

Did a factory restore from within clockwork after clearing Dalvik & system caches, Have installed stock vzw rom from bottom of this page, but am sort of stuck at this point, as I cannot locate a stock Recovery.img to follow the instructions exactly

ok I a confused, the instructions between the two links don't sound right.
and I did find a signed recovery image, it's inside the stock vzw package I linked...... so I am loading it twice?? that's confusing... could really use another person here and not just me in my own head... tho writing this all down could be therapeutic for some I guess

Making a new post for this issue since the title for this post does not reflect the issues currently.

continuing search for answers in this post here entitled more accordingly to the issue

No sim cards detected after OOS 3.2.0

Hi,
I was on OOS 3.1.3 (rooted).
I installed the latest 3.2.0 by:
wiping cache/dalvik
installing full .zip 3.20 via TWRP (downloaded via the amazon aws link)
wiping cache/dalvik
Flashing SuperSU
wiping cache/dalvik
Reboot
Everything seems fine but my phone says no sim card installed. The baseband in About is unknown. And I can't open the screen which shows the IMEI etc on my phone.
Is my EFS wiped out? I made a backup so should be ok. But I am confused as to how to proceed on this?
I have tried to fix this by:
1. Trying to restore the EFS backup using the "fastboot flash modemst1 modemst1.bin" commands (same for modemst2.bin) - I had made a backup of EFS earlier. It doesn't seem to do anything and when I reboot, there is still no baseband.
2. Trying to flash the full ROM zip again - without success
Before I proceed to do anything further, I am hoping someone more intelligent than me can shed some light as to what may have gone wrong and what I can do about it, instead of me managing to make things worse.
Any help would be much appreciated!

Where u got 3.2.0 ? never heard about it

http://forum.xda-developers.com/oneplus-3/how-to/rom-update-to-oxygenos-3-2-0-received-t3410714

I used the same method and the same file and everything is fine here, no apparent issues and I can make/receive calls fine, so the file is ok.
Have you tried rolling back to a previous backup to see if everything works again before trying to reflash?

Hmm, I didn't have much on my phone so decided not to take any nandroid backup. Wasn't expecting any problems (stupid of me, I know).
Hearing all the reports of things being fine, I think the file itself is fine. However, my phone definitely is not. I am truly at my wit's end on how to fix it.
On further discovery, I have noticed that my TWRP has been overwritten with the standard recovery.

PhoenixAG said:
On further discovery, I have noticed that my TWRP has been overwritten with the standard recovery.
Click to expand...
Click to collapse
Well that sounds really odd, and didn't happen on mine, TWRP was still in place for me after the update.

Yes, the whole thing is odd. But I swear I followed the same basic steps as everyone else to try and install the new version.
It's really got me worried, specially the part where I try and restore EFS and everything seems to flash fine, but it doesn't work. I am now trying to sideload the previous version using the default recovery, but its stuck at 92%.

PhoenixAG said:
Yes, the whole thing is odd. But I swear I followed the same basic steps as everyone else to try and install the new version.
It's really got me worried, specially the part where I try and restore EFS and everything seems to flash fine, but it doesn't work. I am now trying to sideload the previous version using the default recovery, but its stuck at 92%.
Click to expand...
Click to collapse
Good luck mate.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

PhoenixAG said:
Yes, the whole thing is odd. But I swear I followed the same basic steps as everyone else to try and install the new version.
It's really got me worried, specially the part where I try and restore EFS and everything seems to flash fine, but it doesn't work. I am now trying to sideload the previous version using the default recovery, but its stuck at 92%.
Click to expand...
Click to collapse
What about sideloading an older Oxygen Version?

same thing happened to me too. After Nandroid restore everything back to normal. I am wondering if my TWRP is wrong somehow...using 3.0.2-0

Same thing happened to me too. I flashed back to 3.1.2 and it's working again.
Edit: There's also people in the OnePlus forums having this issue: https://forums.oneplus.net/threads/oxygenos-3-2-0-ota-sim-problem.453972/

same here, no sim and phone get's hot
how did you downgrade?

Want model number did you have? A3000 or A3003 ?
Sent from my ONEPLUS A3000 using Tapatalk

Guys, I managed to sideload version 3.1.3 back using the ADB sideload on the stock recovery, which I automatically received (don't know how).
All my data is safe and it feels like nothing happened, everything works. Hmm, I am now using adb sideload to just flash the OTA (~400MB) and checking what happens. If it works or doesn't work out, will report back!

DooMMeeR said:
same here, no sim and phone get's hot
how did you downgrade?
Click to expand...
Click to collapse
I flashed this image from TWRP: https://www.androidfilehost.com/?fid=24591020540823765
PLONTER said:
Want model number did you have? A3000 or A3003 ?
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
A3003.
I also downloaded the OTA with the builtin updater and the hash is equal to the one from here: https://www.androidfilehost.com/?fid=24591020540823766
Those links are from this thread: http://forum.xda-developers.com/oneplus-3/how-to/mirrors-official-oxygen-os-roms-ota-t3410870

Dam4rusxp said:
I flashed this image from TWRP: https://www.androidfilehost.com/?fid=24591020540823765
A3003.
I also downloaded the OTA with the builtin updater and the hash is equal to the one from here: https://www.androidfilehost.com/?fid=24591020540823766
Those links are from this thread: http://forum.xda-developers.com/oneplus-3/how-to/mirrors-official-oxygen-os-roms-ota-t3410870
Click to expand...
Click to collapse
A3003 here as well. No Sim detected...

I haven't checked my model number yet - should have. So I side loaded the OTA and its the same result. Phone starts burning hot and no sims detected.
So now I am back to sideloading 3.1.3 yet again. Wish they take out a proper fix for our phones, as I suspect mine is A3003 as well.

You can try to take out the modem file from the zip and try.
Sent from my ONEPLUS A3000 using Tapatalk

Do you have two sim cards or just the one? If two cards, try removing one. If just one, try changing sim card slot.

Potentially bricked? Sprint M9 unable to take OTA

Good evening folks. I am in desperate need of expert advice on this subject.
I imagine that other users have encountered this issue, and this thread may be useful in the future to the assistance of others.
I am rooted, and S-off (as of yesterday). Yesterday, I had TWRP 2.8.7 installed, with stock sense (and sprint bloatware), running android 5.0.1, on firmware 2.11.651.19
*** STILL UNSOLVED*** At first, I was prompted to do a system update (1 of 2), in order to prepare my device for android 6.0. Upon download completion of the first update, and when attempting to install, I am brought back to HBOOT, and the update is nowhere in sight, even when rebooted.
This is a constant loop, and always brings me back to HBOOT.
This is what I have been trying to figure out, and it has got me in an enormous mess ***
*** UNLOCKED ***
htc_himawhl PVT-SOFF
CID-SPCS_001
LK-1.0.0.0000
[email protected]
OpenSDP-15.6.1.00522.8994_1026
OS-3.41.651.4
Feb 3 2013,13:49:48(695981)
Let me describe my problem before I get into detail.
It started when I got my M9, I got it from Sprint, and instantly wanted to root it and install Cyanogenmod 13 on it.
To my mistake, I rooted the phone BEFORE I did the OTA update to Android 6.0
As we know, this is a block based system, and this introduces many difficulties.
I had been running TWRP 2.8.7, and stock sense with all my pre-loaded Sprint crap. I was unable to install cyanogenmod 13 or anything.
This led to much frustration, research, and pain as I browsed countless threads on the XDA forums, downloading many items, hoping they would fix my issue.
Now, for my issues.
The HTC RUU for my phone has never worked, and I was constantly met with ERROR 155. I attempted to re-lock the bootloader, but this made no difference.
Often, when I type in adb devices into the command prompt, I am prompted with something like "you are using a different version than the server... Daemon started.. Then devices: and then nothing. This is what I usually get:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It is obvious to me that if no device is detected, then no work may be done on the phone.
Other times, the phone will recognize, but it seems as if there is no effect on what I am trying to do.
Last night, I paid sunshine $25 to S-off my phone, hoping that it would help me. While the S-off process was extremely easy with this service, my problems are not remedied.
I saw that to restore my phone to 100% stock, that I must complete a RUU with my device, renamed to 0PJAIMG.img, and move it to the SD card.
When I did this, I was still running Stock sence, and was able to move files to my SD card/External SD card.
I went into the bootloader and the phone recognized that I had a "0PJAIMG.img" file on my phone, but I used the wrong file. I used a 75mb file with the firmware, but not all of the sprint things with sense installed. I assumed that since this was the latest firmware, it would allow me to keep Sense and my files, and allow me to take the OTA update to the latest android version
Here are images with information to the INCORRECT "0PJAIMG.img" (that I had renamed from this screenshot) I installed on my phone using the bootloader.
You can see the CORRECT file at about 2GB, and the incorrect file at 75mb.
For reference, Here is what is included in the 75mb file.
Now, I am unable to connect my phone to adb, as it shows up as in the pictures.
I have no recovery installed, so the Stock HTC (and very basic) recovery is there.
I am continuously prompted to install the INCORRECT 0PJAIMG.img that I placed on my phone, and I have no way to remove it as I know.
When I boot normally, I see the HTC One logo, and then a black screen. The screen is still on, but completely black. There is no way to exit this, other than pressing all buttons for 5+ seconds.
I do have the correct 0PJAIMG.img (2gb file), but I have no way of switching these two files, since I cannot connect.
I cannot install TWRP due to no devices showing up in the ADB interface.
When I plug my phone into my computer, I do get the "connected" noise from windows.
Please let me know if I can be more specific. I am going on a trip soon, and will take whatever lengths to get my phone working again.
I have read all relevant threads that I know of, so please avoid re-directing me to another page unless you think I have perhaps missed something.
My end-goal is to have a fully functional HTC M9 with Cyanogenmod 13 snapshot installed. I am on sprint, so I am unsure if I can even use Cyanogenmod. My alternative preference would be the D-Boyz mod to sense.

UPDATE:
I am able to install TWRP 2.8.7.1, and play with that. It seems that when restoring from my old backups, I have the same firmware and OS.
Only now, my radio is bricked.
I have attempted to re-create this, after many painstaking "optimizing apps" runs.
I am currently in a "android is starting"... process.
I will keep this thread updated with information as I progress. I hypothesize that my radio will still be broken.
I am absolutley at my wit's end with this device. I should have never upgraded from the HTC M8. I miss you baby.
I am tempted to take my phone back to sprint. I paid for the S-Off though, and would like to avoid this if possible.
All I want is android 6.0 and CG13.... I'm sick of being annoyed by the "system update is available" notification constantly.
*** STILL UNSOLVED*** At first, I was prompted to do a system update (1 of 2), in order to prepare my device for android 6.0. Upon download completion of the first update, and when attempting to install, I am brought back to HBOOT, and the update is nowhere in sight, even when rebooted.
This is a constant loop, and always brings me back to HBOOT.
This is what I have been trying to figure out, and it has got me in an enormous mess ***

Solved by flashing the ZIP of the RUU for the latest version, placing it on the base of the Phone storage, and naming it "0PJAIMG.zip"

Stuck on setup wifi connecting even after changing roms

I had Redmi note 5 whyred with MUI global rom 10.2.1 (Oreo) with unlocked bootloader and rooted with the latest twrp.
After I deemed the latest miui update not worth it so I decided to flash Pixel experience extended on my phone. First I had to flash the latest firmware available (10.3.2.0) on my phone so I can flash the pie version of PEE, first boot got stuck on google logo fixed on a second flash attempt by reflashing twrp img after flashing the firmware. By after I got to the set I noticed the phone not detecting my sim card which was there so I skipped to wifi, the wifi kept searching without detecting any and when I go to advanced wifi setting my mac address and IP are blank ( check included picture). So I tried reflashing the same rom, then tried to flash another rom (bootleggers) but always ended up in the same result, not detecting wifi and can't skip to home screen.
Another solution I tried is flashing persist.img (taken from fastboot rom 10.3.2.0) through orangefox recovery since it should fix the wifi not working but that also failed.
If there is any other option or solution plz let me know, I can't afford to lose this phone, thank you in advance
Picture for the problem included down
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Your EFS (+modem) partition is corrupted ...do u have a backup? (TWRP Backup?)...I know this cause I have the same issue....for about 2 months now...Hope you get a fix..

rtm2000 said:
Your EFS (+modem) partition is corrupted ...do u have a backup? (TWRP Backup?)...I know this cause I have the same issue....for about 2 months now...Hope you get a fix..
Click to expand...
Click to collapse
I lost my backup after I got a twrp password that encrypted my data and solve it like an idiot by wiping my internal storage. Can I find a way to flash it like persist.img ? or does flashing stock rom via fastboot fix it since it's the only thing I haven't tried yet
Edit: looks like you are right, I have found this methode which I'm gonna try and keep you updated, perhaps we'll be both saved
https://www.theandroidsoul.com/fix-...d-wifibluetooth-issues-restoring-twrp-backup/
Edit2: Didn't do much

Rarohd said:
I lost my backup after I got a twrp password that encrypted my data and solve it like an idiot by wiping my internal storage. Can I find a way to flash it like persist.img ? or does flashing stock rom via fastboot fix it since it's the only thing I haven't tried yet
Edit: looks like you are right, I have found this methode which I'm gonna try and keep you updated, perhaps we'll be both saved
https://www.theandroidsoul.com/fix-...d-wifibluetooth-issues-restoring-twrp-backup/
Edit2: Didn't do much
Click to expand...
Click to collapse
The thing is that I have tried almost all methods available online none seem to work...
My only hope is to get it restored by cell phone repair shops as they have access to tool boxes (miracle,umt etc.)..
Lets see what happens...also dont flash miui cause then you wouldnt be able to verify your mi account if the issue doesnt get resolved...you would be completely stuck..

rtm2000 said:
The thing is that I have tried almost all methods available online none seem to work...
My only hope is to get it restored by cell phone repair shops as they have access to tool boxes (miracle,umt etc.)..
Lets see what happens...also dont flash miui cause then you wouldnt be able to verify your mi account if the issue doesnt get resolved...you would be completely stuck..
Click to expand...
Click to collapse
Hello rtm, I fixed mine I'm using a costum tom and it's up and running as it should be.
All I did was flashing the latest fastboot rom via miflash ( flash all bat and kept the bootloader open) and just like that my phone was fixed, only thing to keep in mind is it asked me ofc about my MIaccount which I miraculously remembered the password and the mail.
Hopefully this will be helpful and you'll find your fix soon as I know how much frustrating the situation you're in now.

Rarohd said:
Hello rtm, I fixed mine I'm using a costum tom and it's up and running as it should be.
All I did was flashing the latest fastboot rom via miflash ( flash all bat and kept the bootloader open) and just like that my phone was fixed, only thing to keep in mind is it asked me ofc about my MIaccount which I miraculously remembered the password and the mail.
Hopefully this will be helpful and you'll find your fix soon as I know how much frustrating the situation you're in now.
Click to expand...
Click to collapse
Thanks for the reply...but in my case custom roms just bootloop without any reason...also flashing via mi flash tool gives the antirbpass error even though I flash an anti 4 rom over an antti 4 rom ...no idea y this happens...
Anyway good to know ur device got fixed...cheers