[Q] [HBoot] How to upgrade Hboot 1.32, Radio and S-Off - HTC One X+

i everyone,
I have just bought HOX+ (AT&T) a few days ago and I totally love its design and performance. I followed THREAD HERE and HERE to unlock bootloader, root and flash radio. This is the result.
{
"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"
}
So far, my phone works like a charm as I expected, hence, I'm really appreciate the job and endeavor of the developers here. I want to thank all of you once again.
Now this is my concern, and sorry for my bad English, I will try to demonstrate the issues as clear as i can.
1. As you can see on the pic, my HBoot is 1.32.0000. I want to upgrade it to 1.35 or 1.4. I did search about 3 hours about that, unfortunately I don't find the solution yet. Additionally, do you recommend me upgrade to 1.34 or 1.4. If I do so, may i lost everything in my "SD card" location. I really have a lot of data in that location and don't want to copy all the data again :crying::crying:.
2. I have followed [RADIO MOD] THREAD in order to flash the radio 2.14. When i checked in setting-about-software information-more-baseband, I see my baseband is 2.14. However, as you can see in the pic, my radio is still 1.09. Do i misunderstand something ?
3. The bright side is that I have S-OFF :angel:. Is it normal or I'm lucky :fingers-crossed::fingers-crossed:. Moreover, with that S-Off, can i help the community by any chances? I mean that can i flash any rom without flashing boot.img and test new rom? Are there any advantages with that S-Off?
My warmest regards.

I recommend sticking with 1.32

sixcarnage said:
I recommend sticking with 1.32
Click to expand...
Click to collapse
Yup, would you please give me some reasons? I just want to know more about the hboot. Why does in Backout rom, it recommend Hboot.14?

Well first off compatability with aosp based roms will not work correctly when fixed. 2, people.day there isn't much of a difference in performance or battery.
---------- Post added at 11:24 PM ---------- Previous post was at 11:22 PM ----------
Also on the blackout rom I am the one who beta tested with 1.32 hboot and none of the apps.would open and I would get an insane amount of reboots. Blackout Mongoose is based on the official update that required the hboot update.

sixcarnage said:
Well first off compatability with aosp based roms will not work correctly when fixed. 2, people.day there isn't much of a difference in performance or battery.
---------- Post added at 11:24 PM ---------- Previous post was at 11:22 PM ----------
Also on the blackout rom I am the one who beta tested with 1.32 hboot and none of the apps.would open and I would get an insane amount of reboots. Blackout Mongoose is based on the official update that required the hboot update.
Click to expand...
Click to collapse
Unfortunately, I want to flash Blackout Mongoose rom for experiencing sense 5. Can you help me to upgrade Hboot 1.4.
Also, how're about the radio?

Well RUU will update it all but wipe everything in the process.

sixcarnage said:
Well RUU will update it all but wipe everything in the process.
Click to expand...
Click to collapse
I have flashed RUU in this thread already. So that is the issue making me confused . Any suggestion?

That's just the rom from the RUU. Download this here http://dl3.htc.com/application/RUU_....55.01_18.21.95.55L_release_310178_signed.exe
---------- Post added at 12:29 AM ---------- Previous post was at 12:27 AM ----------
Notice this is an exe. Before using you must flash the stock recovery img and lock the bootloader. Before locking the bootloader make sure you have the unlock_code.bin from HTCdev.

sixcarnage said:
That's just the rom from the RUU. Download this here http://dl3.htc.com/application/RUU_....55.01_18.21.95.55L_release_310178_signed.exe
---------- Post added at 12:29 AM ---------- Previous post was at 12:27 AM ----------
Notice this is an exe. Before using you must flash the stock recovery img and lock the bootloader. Before locking the bootloader make sure you have the unlock_code.bin from HTCdev.
Click to expand...
Click to collapse
Yup, many thanks.:good:

sixcarnage said:
That's just the rom from the RUU. Download this here http://dl3.htc.com/application/RUU_....55.01_18.21.95.55L_release_310178_signed.exe
---------- Post added at 12:29 AM ---------- Previous post was at 12:27 AM ----------
Notice this is an exe. Before using you must flash the stock recovery img and lock the bootloader. Before locking the bootloader make sure you have the unlock_code.bin from HTCdev.
Click to expand...
Click to collapse
Please correct me if I wrong in any steps
1. Use All-In-One Toolkit V2.3 to relock bootloader
2. Flash Stock Recovery. I found a thread in here or where can i find stock recovery for AT&T?
3. Run exe file and follow it.
4. After flash RUU, unlock bootloader, use the unlocked code form HTCDev.
5. Custom recovery and Root.
6. Done.
Is that right?
-------------
Edited:
Nevermind, i found it HERE. Thank you!

This problem was solved. Thank you.

Related

[Q] Flash splash screen on hboot 1.12?

Hello xda, I have recently tried to flash a custom splash screen using this web converter and it didn't work. My rooted EVO LTE currently has:
HBOOT 1.12.2222
LazyPanda S-Off
TWRP Version 2.2.0
HW Version 0003
SW Version 2.13.651.1 710RD Android 4.0.4, Sense 4.1
Baseband Version 1.12.11.0809
Is there some alternative way to create a custom splash screen and flash it either via recovery or fastboot for 1.12 HBOOT devices?
You could just drop it in to system media
om4 said:
You could just drop it in to system media
Click to expand...
Click to collapse
He is asking about splash screen, not bootanimation.
Sent from my lair.
---------- Post added at 03:15 PM ---------- Previous post was at 03:14 PM ----------
gnarlynick said:
Hello xda, I have recently tried to flash a custom splash screen using this web converter and it didn't work. My rooted EVO LTE currently has:
HBOOT 1.12.2222
LazyPanda S-Off
TWRP Version 2.2.0
HW Version 0003
SW Version 2.13.651.1 710RD Android 4.0.4, Sense 4.1
Baseband Version 1.12.11.0809
Is there some alternative way to create a custom splash screen and flash it either via recovery or fastboot for 1.12 HBOOT devices?
Click to expand...
Click to collapse
What was your flashing process?
Sent from my lair.
The splash screen? I remember doing that for the boot animation. What is the exact directory for splash screens?
Sent from my HTC EVO 4G LTE using Tapatalk
Sorry, got confused. For some reason I always think boot animation when someone says splash screen
gnarlynick said:
The splash screen? I remember doing that for the boot animation. What is the exact directory for splash screens?
Sent from my HTC EVO 4G LTE using Tapatalk
Click to expand...
Click to collapse
You are confusing me, the converter that you posted a link to is for slash screens. Then you asked about bootanimation. What's exactly that you're trying to do?
Sent from my lair.
Op wants splash, I confused everyone lol
volk9029 said:
What was your flashing process?
Sent from my lair.
Click to expand...
Click to collapse
The web generator takes an image you create to exact dimensions and converts it into a flashable .zip folder. From there, you place it on the root of your SD and flash it from recovery. It flashes and says success but when I reboot it has the stock splash screen still displayed. If you read that thread for the web generator that I linked in the OP, on the third page someone states that he/she doesn't believe it works for 1.12 Hboots. I was curious if we had a similar, alternative method for 1.12 in which I can create my own and flash it successfully.
There's no reason you shouldn't have access to splash with soff
gnarlynick said:
The web generator takes an image you create to exact dimensions and converts it into a flashable .zip folder. From there, you place it on the root of your SD and flash it from recovery. It flashes and says success but when I reboot it has the stock splash screen still displayed. If you read that thread for the web generator that I linked in the OP, on the third page someone states that he/she doesn't believe it works for 1.12 Hboots. I was curious if we had a similar, alternative method for 1.12 in which I can create my own and flash it successfully.
Click to expand...
Click to collapse
I had no problem flashing it from recovery. I am s-off and hboot 1.12.2222. Maybe try to flash one of already made from that tread, just to see if you made a mistake when using converter?
Sent from my lair.
om4 said:
There's no reason you shouldn't have access to splash with soff
Click to expand...
Click to collapse
I'll give it another shot when I get home, but I'm under the assumption that hboot version plays a role in changing the splash screen.
Sent from my HTC EVO 4G LTE using Tapatalk
It blocks the partition when locked but seeing as you are s-off it shouldn't matter. Can you peek inside the zip from what ever file explorer you use
---------- Post added at 02:54 PM ---------- Previous post was at 02:37 PM ----------
Sorry my mind is still else where if zip had been damaged flashing would have failed
OK I did it again and it worked without a hitch, don't know what was the issue before. The generator says it checks if the image is in the correct format, dimensions etc. If it is not, it will generate an error code so there was no error there with my upload. Then when I flashed it before it didn't show any errors and said it successfully flashed but it in fact did not. Now I did the same process with the same image and everything worked fine. Thanks for the help guys, whoever said hboot 1.12 wasn't supported was in fact wrong.
Here is the splash I made if anybody is interested, I think it looks classy and doesn't burn your eyeballs out when you look at it in a dark room.
{
"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"
}

Need some advice on upgrading

Currently I'm on a discontinued ROM SkyFall which works fine. I've used xposed to customize to my liking. It's a 1.58.502.1 base rom. What would be the advantages to upgrading to a 4.4.3 rom or higher based rom like Sky Dragon? Will I see enough improvements or additions to warrant the hassle of backing up everything and starting fresh? Any thoughts appreciated. P.S. Only talking about stock roms, not interested in any others.
Well I was using Viper One and missed the feel of my Nexus 5 so I to chose Skydragon and its definitely worth it.here is some pics of the Skydragon version I run and a pic of how small the System is .simple and smooth.
{
"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"
}
Oh and I'm on the same firmware base
Well there is a sinless sense version, but I'm not sure if its been updated lately..I'm pretty sure you'd need to update your firmware though
---------- Post added at 04:45 AM ---------- Previous post was at 04:44 AM ----------
this is InsertCoin (Sense)
http://forum.xda-developers.com/showthread.php?t=2704539
Here's Sinless (Sense)...
http://forum.xda-developers.com/showthread.php?t=2722578
jxcorex28 said:
Well there is a sinless sense version, but I'm not sure if its been updated lately..I'm pretty sure you'd need to update your firmware though
That's the main issue. I've been looking at the international roms but someone mentioned that they don't play well with our radio. Now that 4.4 is out I really want to upgrade my firmware but it looks daunting according to the forums. I really need a good guide to walk me through. I've read a few guides in the international forums but they are a little vague. I'm s-off and could go super cid if needed. Do I just download a firmware off the forums and fastboot flash or is there more to it?
Click to expand...
Click to collapse
I just flashed the T-Mobile L24G radio and my data is doing great.
S-OFF and Supercid required
Radio link
http://forum.xda-developers.com/showthread.php?t=2736921
http://forum.xda-developers.com/showthread.php?t=2824048
Take a look at the above link. The links created by Skulldreamz...He doesn't have the latest .7 firmware included though. I'm sure he'd be able to help you get it. With these zips (included on the 1st page). The easiest and most hassle way of flashing these firmware zips is naming the zip (0P6BIMG.zip), and flashing while in boot loader mode...you can also remove the contents of other firmware zips. Using a file explorer such as ES or Solid Explorer, delete the recovery .img and boot.img. then rezip the file,rename to 0P6BIMG, and flash in bootloader
---------- Post added at 11:55 PM ---------- Previous post was at 11:48 PM ----------
You should ask skulldreamz about the tmobile firmware he's included in his thread. Skulldreamz removed the recovery.img from those zips (I believe). If you had a custom revovery, then you flashed a firmware zip that hadn't been modified and still contained the recovery.img. you could have unexpected results. If you flash a firmware zip like that you have to fastboot flash another recovery omg after you flash the firmware zip. You're on Tmobile, so it's best to ask skulldreamz,mike1986, or sneakyghost as those guys are more knowledgeable on firmwares
---------- Post added at 11:58 PM ---------- Previous post was at 11:55 PM ----------
Do not flash AT&T firmware on a T-Mobile phone. I do not know if having s_off alone will work. I don't know what would happen, but I'm sure nothing good would happen...ask the guys I mentioned in my previous replies...
Flashed ROM and radio and have no issues at all
Nice...did you find T-Mobile firmware ?
jxcorex28 said:
Nice...did you find T-Mobile firmware ?
Click to expand...
Click to collapse
Who are you asking ?

rooted hct one x+ at&t - can't do anything

Hello guys I tried to make a Unroot, change the ROM, since it has android 4.2 and I want to update it for compatibility, this htc I bought it used and I was already rooted, I do not know how they did the procedure, I add a photo of the information that comes out when I do The fastboot.
If anyone knows I can do that whenever I try something stays on the white screen of HTC and waited until almost an hour and nothing happens.
tks:fingers-crossed:
{
"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"
}
From that screen you can't tell if the phone is rooted or not. have you tried going into Recovery mode? The device has obviously had the bootloader unlocked, from this point, you could flash a recovery, assuming the phone doesn't have one, and from there flash a custom ROM (make sure it's for the AT&T version of the phone). Android 4.2 is the newest OS, unless there is custom ROM out there, but I haven't seen one on the XDA forums. Also make sure you are flashing everything correctly.
Alternatively, you could run the RUU to reset the phone to factory specs. You will have to re-lock the bootloader. I have the most recent one somewhere.
Capt'n Mal said:
From that screen you can't tell if the phone is rooted or not. have you tried going into Recovery mode? The device has obviously had the bootloader unlocked, from this point, you could flash a recovery, assuming the phone doesn't have one, and from there flash a custom ROM (make sure it's for the AT&T version of the phone). Android 4.2 is the newest OS, unless there is custom ROM out there, but I haven't seen one on the XDA forums. Also make sure you are flashing everything correctly.
Alternatively, you could run the RUU to reset the phone to factory specs. You will have to re-lock the bootloader. I have the most recent one somewhere.
Click to expand...
Click to collapse
i tried to make a factory reset, install new ROM, and a lot of things more, i'm going to make more hopefully someone work.
tanks for the answer
I have 2 of these. Pre released HTC one x+ evitare
---------- Post added at 12:32 AM ---------- Previous post was at 12:32 AM ----------
jdgcol said:
Hello guys I tried to make a Unroot, change the ROM, since it has android 4.2 and I want to update it for compatibility, this htc I bought it used and I was already rooted, I do not know how they did the procedure, I add a photo of the information that comes out when I do The fastboot.
If anyone knows I can do that whenever I try something stays on the white screen of HTC and waited until almost an hour and nothing happens.
tks:fingers-crossed:
Click to expand...
Click to collapse
OMG u have 1.73 bootloader. Wth? Lol
---------- Post added at 12:34 AM ---------- Previous post was at 12:32 AM ----------
Capt'n Mal said:
From that screen you can't tell if the phone is rooted or not. have you tried going into Recovery mode? The device has obviously had the bootloader unlocked, from this point, you could flash a recovery, assuming the phone doesn't have one, and from there flash a custom ROM (make sure it's for the AT&T version of the phone). Android 4.2 is the newest OS, unless there is custom ROM out there, but I haven't seen one on the XDA forums. Also make sure you are flashing everything correctly.
Alternatively, you could run the RUU to reset the phone to factory specs. You will have to re-lock the bootloader. I have the most recent one somewhere.
Click to expand...
Click to collapse
Got any roms for this floating around? Lol
---------- Post added at 12:35 AM ---------- Previous post was at 12:34 AM ----------
jdgcol said:
i tried to make a factory reset, install new ROM, and a lot of things more, i'm going to make more hopefully someone work.
tanks for the answer
Click to expand...
Click to collapse
Just flash 2.8.0 twrp

[RECOVERY][UNOFFICIAL][Deen] TWRP

We have finnaly gotten TWRP for the Motorola One Deen
https://androidfilehost.com/?fid=11410963190603888689
ALL CREDIT GOES TO @Alberto97 FOR MAKING TWRP FOR A DEVICE THAT HE DOESN'T OWN!
How to flash:
You need ADB fastboot files
You need an Unlocked Bootloader: https://www.youtube.com/watch?v=_Zhqfzg__IA "full tutorial"
The recovery image: "link above"
Command: fastboot boot twrp-deen-0.img
Your warranty is Void!
I'm NOT responsible for broken devices or anything that will happen resulting booting twrp.
For some reason i have to explain that this it not flashing. It's booting. You need to use the command to boot to twrp every time.
https://androidfilehost.com/?fid=11410963190603868607
Update!
Thank you very much for your effort, will try it out soon.
However just out of curiosity, is it not possible to use the official TWRP for the Moto One Power (chef) https://twrp.me/motorola/motorolamotoonepower.html ?
I would assume those two phones are very similar in terms of partitions.
actually I just saw that Tys0n indeed used a "chef" based TWRP image on his root attempt ( link ) , I assume using this updated one from Alberto should be even better.
p-walker said:
actually I just saw that Tys0n indeed used a "chef" based TWRP image on his root attempt ( link ) , I assume using this updated one from Alberto should be even better.
Click to expand...
Click to collapse
It shouldn't even boot. It's 2 completely different devices with 2 different chipsets. So no. This one is built using our device sources
Slot a or b
---------- Post added at 08:08 PM ---------- Previous post was at 08:03 PM ----------
What I can do?
does not enter bootloader
I tried to install twrp and magisk
when I installed magisk, he died
{
"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"
}
Danielikto said:
Slot a or b
---------- Post added at 08:08 PM ---------- Previous post was at 08:03 PM ----------
What I can do?
does not enter bootloader
I tried to install twrp and magisk
when I installed magisk, he died
Click to expand...
Click to collapse
If it doesn't enter bootloader, its Hard bricked
p-walker said:
actually I just saw that Tys0n indeed used a "chef" based TWRP image on his root attempt ( link ) , I assume using this updated one from Alberto should be even better.
Click to expand...
Click to collapse
I've never used any file for chef. I just linked to bootloader unlock guide in chef forum
Sent from my H9436 using Tapatalk
borksek said:
If it doesn't enter bootloader, its Hard bricked
Click to expand...
Click to collapse
Do you know how to fix it?:crying::crying:
tys0n said:
I've never used any file for chef. I just linked to bootloader unlock guide in chef forum
Sent from my H9436 using Tapatalk
Click to expand...
Click to collapse
Sorry my bad, misunderstood your comment then.
Danielikto said:
Do you know how to fix it?:crying::crying:
Click to expand...
Click to collapse
Your phone is destroyed. You have to get a new one
help me. i wont stock ppk29.68-16-8 and how it flash?
I have the same problem (black screen and only blinking LED when plugged in) after trying to switch the partition slot!
I'll try to see if I can fix this but so far it looks bad :/
---------- Post added at 09:23 PM ---------- Previous post was at 09:13 PM ----------
Small update: the device is in QLOAD mode which apparently can be fixed with https://github.com/jareddantis/unbrick_8960
---------- Post added at 09:59 PM ---------- Previous post was at 09:23 PM ----------
Ok, apparently the recovery can be done with blankflash.
If anyone knows how to get one for the moto one it would be greatly appreciated!
I sent it to guarantee and they gave me a new phone c:
superproskiller said:
I have the same problem (black screen and only blinking LED when plugged in) after trying to switch the partition slot!
I'll try to see if I can fix this but so far it looks bad :/
---------- Post added at 09:23 PM ---------- Previous post was at 09:13 PM ----------
Small update: the device is in QLOAD mode which apparently can be fixed with https://github.com/jareddantis/unbrick_8960
---------- Post added at 09:59 PM ---------- Previous post was at 09:23 PM ----------
Ok, apparently the recovery can be done with blankflash.
If anyone knows how to get one for the moto one it would be greatly appreciated!
Click to expand...
Click to collapse
There is no blank flash. Go back to where you bought the phone and tell them it was done by an update. Usually it is backed up by the warranty
bosh23 said:
help me. i wont stock ppk29.68-16-8 and how it flash?
Click to expand...
Click to collapse
For that you need RetEU Motorola one deen 1941-1. If you don't know how to get this info, you probably shouldn't flash.
Danielikto said:
I sent it to guarantee and they gave me a new phone c:
Click to expand...
Click to collapse
Really? I mean, you agree to avoid warranty when you apply for the bootloader unlock code.
tys0n said:
Really? I mean, you agree to avoid warranty when you apply for the bootloader unlock code.
Click to expand...
Click to collapse
You can always relock and lie ??
borksek said:
You can always relock and lie
Click to expand...
Click to collapse
Not if it's bricked, and the warranty is still gone even if you relock. They just need to check up IMEI to see that you're out of warranty.
It Works On Android pie?

MI A3 wont install updates !!!

hi there
i installed miui xiaomi.eu custom rom but it failed ! after that i flashed stock rom and ot need to change slot to A
from then i can not install any update ( even with flash stock rom )
{
"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"
}
#MmdRza said:
hi there
i installed miui xiaomi.eu custom rom but it failed ! after that i flashed stock rom and ot need to change slot to A
from then i can not install any update ( even with flash stock rom )
Click to expand...
Click to collapse
how did you flash stock rom?
It has few weeks that my stock ROM is having the same problem, MmdRza!
I click to install this ~87MB (in my cased it is precisely 86.4MB) updated and when it finishes I receive the following message in red colour: "Installation will continue when device isn't being used. To install now, tap Resume"
So, when I resume, the same looping occurs. The only thing that I did was root my device =(
Same here
I was screwing with custom roms and eventually decided to roll back to stock.
Installed the stock via twrp, upon first boot it said something is corrupt suggested to do factory restore and booted fine
Just now when I try to update I get the same issue. I personally stuck on V10.3.12.0.PFQEUXM
Someone help us please
Sapper Morton said:
Read this for an explanation about the system OTA, and the importance of firmware integrity . Get back to us if you're not able to update after doing the necessary steps.
Click to expand...
Click to collapse
Thanks mate but instructions were unclear - "download full OTA zip (not the incremental one, size must be above 1gb)"
Not sure were to get this full OTA zip for my EU A3
---------- Post added at 05:10 AM ---------- Previous post was at 04:48 AM ----------
Valiko89 said:
Thanks mate but instructions were unclear - "download full OTA zip (not the incremental one, size must be above 1gb)"
Not sure were to get this full OTA zip for my EU A3
Click to expand...
Click to collapse
After some wandering around I found a google drive link says "payload_V10.3.14.0.PFQEUXM.bin" is this what I was looking for?
---------- Post added at 06:02 AM ---------- Previous post was at 05:10 AM ----------
Valiko89 said:
Thanks mate but instructions were unclear - "download full OTA zip (not the incremental one, size must be above 1gb)"
Not sure were to get this full OTA zip for my EU A3
---------- Post added at 05:10 AM ---------- Previous post was at 04:48 AM ----------
After some wandering around I found a google drive link says "payload_V10.3.14.0.PFQEUXM.bin" is this what I was looking for?
Click to expand...
Click to collapse
Guess im stuck again this time "tune2fs" not found
Valiko89 said:
Thanks mate but instructions were unclear - "download full OTA zip (not the incremental one, size must be above 1gb)"
Not sure were to get this full OTA zip for my EU A3
---------- Post added at 05:10 AM ---------- Previous post was at 04:48 AM ----------
After some wandering around I found a google drive link says "payload_V10.3.14.0.PFQEUXM.bin" is this what I was looking for?
---------- Post added at 06:02 AM ---------- Previous post was at 05:10 AM ----------
Guess im stuck again this time "tune2fs" not found
Click to expand...
Click to collapse
1. collection of Fastboot and OTA images at one place (use Google translate and click on "official firmware" ) http://4pda.ru/forum/index.php?showtopic=962154. Though there are Fastboot images with more recent versions available, so it doesn't make much sense to extract old OTA images yourself (unless you want to try it).
2. tune2fs must be run as root (adb shell; su; tune2fs)
_mysiak_ said:
1. collection of Fastboot and OTA images at one place (use Google translate and click on "official firmware" ) http://4pda.ru/forum/index.php?showtopic=962154. Though there are Fastboot images with more recent versions available, so it doesn't make much sense to extract old OTA images yourself (unless you want to try it).
2. tune2fs must be run as root (adb shell; su; tune2fs)
Click to expand...
Click to collapse
Well that was almost 48H wild ride
lol looks im too dumb to run adb shell as root cuz after adb shell I always got 'not found' also couldn't find the actual up to date ota on 4pda
So I got slightly older ver. ota gave up on the tune2fs step and headed on extracting the system.img from the payload.bin then flashing it blindly using 'fastboot flash system system.img' and when done got thrown back to yesterday - no phone at all just plain xiaomi logo yayyy fml!
But! on the same 4pda I stumbled upon the latest V10.3.17.0.PFQEUXM Fastboot recovery, and after poking around the web re-flashing the whole damn thing with the stock fastboot rom seemed like not such a bad idea at this point of my frustration.
By now the whole a/b slot tuned into one huge salad in my head so I went for sure and this is what I did:
1. boot to fastboot manually
2. 'fastboot flashing unlock' (holding vol down to return back to fastboot)
3. 'fastboot' flashing unlock_critical (holding vol down to return back to fastboot)
4. 'fastboot --set-active=a'
5. flashed the extracted tar folder with MiFlash and holding vol down near finish to return back to fastboot
6. 'fastboot --set-active=b'
7. flashed the same extracted tar folder again with MiFlash and holding vol down near finish to return back to fastboot
8. 'fastboot flashing lock_critical'
9. 'fastboot reboot'
And hooray! It booted to latest updated rom will have to wait for next OTA update to see if it works at all :cyclops:

Categories

Resources