Hi, I've recently rooted my phone and I'm quite happily running InsertCoin ICS ROM. Although I don't have any problems I'm curious to know why when I reboot into the bootloader and select the BOOTLOADER option from the menu is get numerous errors/warnings saying can't find PG58DIAG.zip, PG58DIAG.nbh and a number of other files. Why is this happening, is it merely the bootloader looking for these files so it can update the firmware? I recall having to drop a pg58diag.zip file (I think it was called that anyway) as part of the rooting process.
Finally what do these files update, I understand it's firmware but is it specifically the radio firmware as I've seen various references to updating radio firmware specifically and other references to just firmware as if it applies to more than just the radio.
Sorry if these questions have been asked before but I want to be very clear on what files relate to what when upgrading and also the differences in process to simply flash a new ROM which so far seems dead easy - simply pick a zip file from the SD card within 4ext Recovery and follow the installation instructions. It's only when there are dependencies on other files (such as firmware/radio) that things get more piecemeal and slightly confusing.
Sent from the future three weeks ago.
Related
I see a lot of people repeatedly asking the same questions regarding 2.1/root/etc, so I made an FAQ for them to be referred to. It is located here:
lostsync.net/erisfaq.html
It's perfectly ok with me if it is reproduced in any way. I'm also happy to make changes and corrections.
Following jcase's advice, the full text is also posted below:
__________________________________________________
What is root and why do I want it?
On UNIX-like systems, root is generally the only account that can do anything it wants without restriction. The root account is often disabled or access is not given to the end user for security reasons. Rooting a phone (or anything else, really) refers to obtaining root access through whatever means available. A person would want to root their phone because it allows for capabilities beyond those provided in the original software and gives third-party apps new possibilities (like wireless tethering, for example). It also allows the user to flash custom ROMs, boot images, and otherwise tinker with their phone in ways that it was not designed to let you do. If you are familiar with iPhone/iPod Touch jailbreaking or softmodding a game console, you can consider rooting analogous for all intents and purposes.
Can I root my phone?
Yes, Whether your phone is running 2.1 or 1.5 you can root it using this method
If I have 2.1 leak on my phone, can I root it?
Yes
What versions of 2.1 exist?
There are three 'official' versions of 2.1. These are generally referred to as 2.1 root, 2.1 leak, and 2.1 ota (or new 2.1 leak).
What version of 2.1 do I have?
The easiest way to determine this is to go back to where you got 2.1 and re-read. Barring that, use the following steps:
From the home screen, press the menu key
Select "Settings"
Select "About Phone"
Select "Software Information"
If you see "release-keys" under the "Build Number" heading, you have some version of 2.1leak. If you see "test-keys," you have 2.1root or some derivative of it (i.e. a custom ROM)
Is it possible to downgrade from 2.1 to 1.5?
Only if your phone is already rooted.
Is it possible to upgrade from 1.5 (rooted) to 2.1 and keep root?
Yes.
If I install 2.1leak (or any version of 2.1 currently available), will I be able to receive the OTA update from Verizon when it comes?
Nope
I have installed some version of 2.1. Some apps don't appear in the Market. What gives?
Use this tool made by Jcase
Can I install a custom ROM without root?
No.
I have root. How do I install a custom ROM?
Read Here and Here
Does <some custom ROM> contain <some feature I want>?
Check with the person or people responsible for the custom ROM in question.
Can you explain all this talk about signed ROMs?
It goes something like this: When HTC is ready to release a firmware version, they sign it. They do this by first creating something like an MD5 checksum based on the original contents of the file. That checksum is then encrypted with a key pair belonging to HTC. When the phone tries to flash firmware, it first decrypts the checksum using keys installed on the device. That checksum is compared against the firmware package you are trying to flash. If it matches, firmware installation can proceed. If not, the firmware is assumed to be broken, corrupt, or hacked and is rejected. Nobody outside of HTC knows exactly how they sign their ROMs and the above is really just an educated guess. This makes it difficult, if not impossible, to reverse engineer the signing process as a way of obtaining root. Even if we did know the exact procedure, it would be very difficult to pull off.
I installed 2.1 leak. When will I be able to root my phone?
Yes, Use this method
How did they get root in 2.1 root?
2.1 root was leaked from HTC and was already rooted. Since no procedure was developed by the devs to root it, it's impossible to apply that procedure to other versions of 2.1 that have been leaked from HTC.
What is a 'gold card'?
A gold card is a memory card that has been converted to unlock your device's CID while it is in bootloader mode. It allows you to essentially turn your production phone (meaning one sold in stores) into a development phone (meaning one used internally at HTC for the development of ROMs), which will let you flash any ROM you like. No one has succeeded in creating a gold card for the Droid Eris.
It would be great if you included the whole FAQ in the post. Good write up.
jcase said:
It would be great if you included the whole FAQ in the post.
Click to expand...
Click to collapse
Good point.
Nice job lostsync. Will definitely be pointing to this thread to help guide the
lost sheep and/or the"too damn lazy".
+1
this is defiantly a very good write-up FAQ. It answers almost all of the common questions new members are asking. i will be pointing to this often!
Sticky!
Great info
Stickying this, and unstickying the other thread. You should add a link to the rooting process, though.
And, of course, thanks for the write up .
Hey,
I have a question. I have read across threads about the issue with modified serial number and am planning to flash the ICS bootloader. However, the question is, if I flash the ICS bootloader manually (I assume that the standard ROM packages do not contain bootloaders) will I still be able to flash downgrade, say to Gingerbread or do I need to flash an older version of the bootloader.
The thing is, the phone still has 6 months of warranty and with changed serial number (IMEI is intact) I do wonder whether this will affect anything if warranty service is required. Another issue is, does Serial Number matter in way official ROMs are being distributed? I'm running a factory unlocked phone (CSC=COA, Cosmote Romania) some people have reported getting 4.0.3, others 4.0.4, which is quite strange. Kies does read the phone properly when I have 4.0.3 with proper CSC, saying that this is the latest software version.
Also, whilst I'm on the subject, if needed, when I flash a ROM which has a bootloader as well, is there any particular order required to flash? Like for instance, flash bootloader first then desired ROM, or can they all be flashed at once (adding APBOOT or whatever it's called on Bootloader in Odin, PDA, MODEM, CSC and .pit if need be).
I've read that playing around with bootloaders can be dangerous if you don't know what you are doing, so if anyone has this kind of experience, it would be appreciated. Could not seem to find any solution to this.
Thanks
good question imo
Darkmind1 said:
Hey,
I have a question. I have read across threads about the issue with modified serial number and am planning to flash the ICS bootloader. However, the question is, if I flash the ICS bootloader manually (I assume that the standard ROM packages do not contain bootloaders) will I still be able to flash downgrade, say to Gingerbread or do I need to flash an older version of the bootloader.
The thing is, the phone still has 6 months of warranty and with changed serial number (IMEI is intact) I do wonder whether this will affect anything if warranty service is required. Another issue is, does Serial Number matter in way official ROMs are being distributed? I'm running a factory unlocked phone (CSC=COA, Cosmote Romania) some people have reported getting 4.0.3, others 4.0.4, which is quite strange. Kies does read the phone properly when I have 4.0.3 with proper CSC, saying that this is the latest software version.
Also, whilst I'm on the subject, if needed, when I flash a ROM which has a bootloader as well, is there any particular order required to flash? Like for instance, flash bootloader first then desired ROM, or can they all be flashed at once (adding APBOOT or whatever it's called on Bootloader in Odin, PDA, MODEM, CSC and .pit if need be).
I've read that playing around with bootloaders can be dangerous if you don't know what you are doing, so if anyone has this kind of experience, it would be appreciated. Could not seem to find any solution to this.
Thanks
Click to expand...
Click to collapse
Was hoping someone would of replied especially the last bit about the order in which to do this. My issue is I have stock 4.1.1 rooted with cwm. I really want to install the new aokp rom from which i understand is 4.2 which he recommends to update the bootloader. I also dont feel (even though I have been reading quite a bit ) that i'd be good on my own to recover from a bricked situation without nagging on devs. Being that I am rooted would installing this new bootloader rid me of my cwm? And should I preform any wipes before flashing the new bootloader.most threads I have read was going from stock not rooted. Given my lack of knowledge not too sure how to proceed.
Good afternoon, XDA community, I've been searching the heck out of Google for an answer to what I'm trying to do, and haven't gotten anywhere.
I have a Motorola Backflip running the latest AT&T firmware, and I'd like to downgrade it back to Android 1.5.
Now, I learned early on the Radio/Bootloader cannot be downgraded. After some digging I've found a thread on ModMyMobile that instructs you on loading the Radio image from the newer firmware into an SBF containing the older Android version. This can then be flashed from RSD Lite, and it'll keep the new radio and bootloader while loading the system partition of old.
However, an update released after that was post was made put the kibosh on that approach. It now refuses anything that isn't an official, signed SBF.
Here's three ideas I think might work, and I'd like your feedback on them:
1.) I have the MBN files extracted from the Android 1.5 SBF sitting on my hard drive. Is it possible to extract the contents of the systemsec.mbn file, load it into a flash-able ZIP; and then flash it via the custom recovery I have on the phone?
2.) If someone out there were to provide me with a backup of the old firmware, created with jr00ds recovery, could it then be modified to remove everything but the system partition, and then simply restore the modified backup to my device?
3.) This is one I know will do the trick: if someone on these forums has an old, battered Backflip that still has Android 1.5 sitting on its ROM, I could just transplant the motherboard to my pristine unit. If any of you have one you're willing to sell cheaply, please let me know!
Before anyone asks the obvious "Why so much effort for an outdated device/version of Android?", it's purely for nostalgia. This was my first Android device, and part of me would like to relive it. Because, frankly, the 2.1 update was just plain terrible.
THIS IS A CLOSED CASE, GO HOME. The answer is Hairybean found in step 2 of here [ROM] [TF201] KatKiss 5.1.1 - v30 [MultiWindow] [Stable] [RRO] Read the rest of this post if you're a sadist or want to know of people in the same pain boat as you.
Part 1: My life's story. Skip to Update if you just want to hear of my current problem.
So approximately 12 hours ago, I decided, "Hey, I want to upgrade my tablet so I can download the newest and coolest apps. Since I need to upgrade to a newer OS (ICS>KK ?) I may as well go through the extra hurdle and download a nice, fast custom ROM because the stock feels like crap for the lightweight that is the TF201."
Now me, not having ever touched an android in my life before this tablet, knew this was going to be a challenge. After doing plenty of research into unlocking, flashing a custom recovery, general custom ROM flashing etiquette, and following this guide ([ROM] [MM 6.0.1] KatshMallow v29 [TF201]), I encountered my first of many hurdles. This being: I was able to boot just fine, but the Wifi was in a perpetual state of "Wifi turning on..." I put a total of a couple or so hours into researching this and easily found others having the same issue, albeit not specifically to the exact ROM and device in question. I also tinkered a bit in these hours, reflashing and rebooting and all that jazz. I eventually settled upon one of three conclusions:
The "/persist" folder had gotten deleted which contains vital wifi/network configuration data
wlan0 was borked on a hardware level and I managed to completely kill an hope of wifi on my device
There was a MAC address somewhere that I needed to manually edit (that WASN'T in the persist file)
Considering the fact that I could not see nor change directory via adb terminal (yes, with su) into a "/persist" folder, and that the hardware-broken devices other users had were most if not all cellphones, I pushed on ahead assuming #1 to be my problem. ("See" includes dropping and installing a file explorer onto the tablet as well.)
With this is mind, the next course of action was to somehow get this "/persist" folder back. It seemed like the best way to do this would be to flash a stock ROM (link in Part 2) or ask the community to give me files without even trying to solve things on my own. So in the spirit of remaining a lurker I chose the former. Flashed fine, booted fine, ran.... okay-ish (the status bar "System UI" would crash every 10 seconds, ROM was a means to an end so I didn't care), but the Wifi WORKED! However, I still didn't find a /persist folder and the tablet didn't show up in windows... "Weird but okay, whatever let's do this." Load up recovery again, wipe everything, see if I can get Katshmallow to load again...
Part 1.5: And here we are. tl;dr I'm a scrub at anything android and after 12+ hours of tom****ery, I'm in a bootloop using Katshmallow v29 (v27 made no difference). The "bootloop" is in the form of the ASUS logo appearing with the usual "UnLocked" message in the top for a minute or two, then a reset, rinse, repeat. I am able to boot into recovery and mess around in TWRP just fine, so my ignorance hasn't completely wrecked me... yet.
The information that I believe is most pertinent to my current issue is:
I unlocked using ASUS' utility for the TF700. It worked no problem and with how compatible things seem to be between the two, I don't think this is an issue (especially considering I've flashed and booted system more-or-less just fine).
The most recent ROM I flashed was this [ROM] TF201 JB JRO03C 10.4.2.15 (US) Stock Deodexed + Mods [Unlocked BL]. I figure that this did something (maybe changed the bootloader?) that Katshmallow does not agree with. If I hadn't already spent the better half of a day working on trying to get things working, maybe I would do more research and figure out the inner workings on my own, but I'm done bashing my head against a brick wall that's only pushing me further back.
I am currently running KANG TWRP 2.8.7.2 for the TF201T (yes, the device I'm specifically running). The problem existed with some TWRP 2.8.x for the TF300 as well.
The bootloader message is "Android card-hu-user bootloader <1.00e> released by "US_epad-10.4.2.15-20120917" A03 ... Oh son of a-
Part 2: So I'm a dumb*** who can't read. Okay, I need to know how to get from my current bootloader (10.4.2.15) to the one Katshmallow requires (10.6.1.27.1). In typing this, I realized that the stock ROM I used to test stuff is why I've been screwed for the past 5 hours (coupled with my ignorance of course). In my quick 2 minutes of research I found this: [GUIDE][13/11]Update/Recovery/Root/Downgrade Android 4.2.1 on Unlocked/Locked Devices. I fancy methods 2 and 3, I can do those, but that doesn't change the fact that I know NOTHING about the bootloader and what I need to update it (but apparently I know how to give myself a headache by downgrading it).
Any help will be greatly appreciated. Oh, and if you know of how to solve the Wifi issue or the likely related /persist folder issue in the wall of text above, please I beseech you to tell me.
Disclaimer: My "research" is not at all limited to the links in the post. I've spent 90% (or more) of what's now probably 13-14 hours working on getting this piece of- getting things to just go right. So... tired...
Update: The problem has changed to my second post that I will be pasting here to save people the trouble:
So the problem as it stands now. I'm cannot seem to flash a different custom recovery and whenever I try to flash a ROM I get "E:Error executing updater binary in zip" The line above it, "symlink: some symlinks failed". I give up for now... Maybe I'll try again tonight. I'm running bootloader 10.4.2.15 and TWRP KANG 2.8.7.2 (which seems to require a 14.10 bootloader). In this mess, I don't know what to fix nor how to fix it. The angles I see are fix the custom recovery or fix the error/symlink problem since the bootloader version seems to be dependent on successfully flashing ROMs.
Update2: So I managed to upgrade the bootloader by somewhat forcefully flashing Hairybean. While Katshmallow said "JB 4.2.1 BOOTLOADER VERSION 10.6.1.27.1," I glazed over this because I didn't know the importance of the bootloader and there was no other mention of the bootloader in the post (no mention of Hairybean or a download link or a "More information" link). I still have no one but myself to blame, just bitter that I have to blame myself in the first place.
For the time being, I'm following the somewhat better instruction on found in this thread([ROM] [TF201] KatKiss 5.1.1 - v30 [MultiWindow] [Stable] [RRO]) and will be picking up Katshmallow at the "wipe" step (currently waiting on the /data format). I downloaded the newest version of TWRP for TF201T and it's working just fine (note how that thread also doesn't mention anything aside from "MUST BE ON THE HAIRYBEAN BOOTLOADER ENDING IN 27.1" While that's such an obvious and blatant statement that should have inspired some research, my ignorance blinded me).
Now that I know for a fact that I am running the right TWRP and the right bootloader, I am going to pray that I can at VERY LEAST flash and boot into Katshmallow. Whether or not the Wifi problem persists will be for another thread.
IT BOOTS! YAAASSS. How do I close this embrassment of a thead?
Sorry I can't be of more help but what I CAN say is:
- read instructions thoroughly with any release. Sometimes a modified TWRP or other file is posted that you must use even if you have a newer version. You might also have to bounce around to other posts along the way to install/update all of the necessary files.
- keep a written log of changes you've made with notes on reversing them. Changing the bootloader means you can't go back unless you revert it back first. I can back track everything I've done based on my own notes, much easier to understand than someone else's notes or directions.
Good luck and be patient. Don't make more than one change at a time and get it working or revert back before trying something totally different.
Sent from my LG-H811 using Tapatalk
HorthLithperer said:
Sorry I can't be of more help but what I CAN say is:
- read instructions thoroughly with any release. Sometimes a modified TWRP or other file is posted that you must use even if you have a newer version. You might also have to bounce around to other posts along the way to install/update all of the necessary files.
- keep a written log of changes you've made with notes on reversing them. Changing the bootloader means you can't go back unless you revert it back first. I can back track everything I've done based on my own notes, much easier to understand than someone else's notes or directions.
Good luck and be patient. Don't make more than one change at a time and get it working or revert back before trying something totally different.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Thank you for replying nonetheless. I'll keep the note thing in mind. Regarding the bouncing around to get the files necessary, I've done plenty of that. When installing a new ROM, I made sure to follow the links as they were given and did further research where things weren't clear. My current problem stems from that fact that, 1: I have no point in which to restore back to due to my aforementioned ignorance and oversight of basic Android terminology; and 2: The next step is to revert the bootloader, that of which I have no clue how to do or where to start since my preliminary google search. Even if I had been taking notes, no one mentions how to do this without a backup. And so I'm on a hunt to find this information and for posterity, I'll post my quest here:
Google search: "tf201 bootloader version"
Upgrading from ICS Bootloader > [ROM] [TF201] [JB Bootloader] CyanogenMod 10 Unofficial - JZO54K - Oct 30 2012 - I learned that apparently certain ROMs can overwrite the bootloader, extrapolated from:
4) Needs the new Jelly Bean 10.4.2.15 bootloader [IMPORTANT: Flashing over an incorrect bootloader can permanently brick you device. The Oct 13 2012 build includes the bootloader upgrade and can be flashed over any ROM/bootloader]
Google search: " update tf201 bootloader"
[GUIDE] How to manually update/restore firmware (TF101, TF201, TF300, TF700, TF701) - Post #2 sent me to ASUS official support wherein I downloaded "V10.4.2.18." This is a test in hopes that I can get a ROM running and see if the bootloader changes. I'm not able to use the methods in that thread as I do not have a system nor a microSD, as such I'll flash it the way I have been. Same custom recovery as before. Run the usual wipe (Dalvik, System, Cache, Data, Internal). Drop ASUS ROM onto pad's internal. Attempt flash... Error: "E:Error executing updater binary in zip"
More research, now trying to find out what this error is. Tried this and read a couple pages from here. Settled on reflashing TWRP. While looking up the command again, I came upon here, then went to the first post of that thread here, then from the TWRP link in that post to here (yes, I see the big TF700T at the top, I also see the big MUST BE ON A BOOTLOADER ENDING IN 14.10).
Okay so, I have 10.4.2.15 and am going to have to jump through several hoops to get to the mysterious 10.6.1.27.1. Annnnd It seems as though I have a custom flash that doesn't support my bootloader (which I feel should've been an issue up until now?) I just want to boot into A ROM, so either I find a ROM that supports the bootloader and probably flash a recovery that does as well...
Googled: "10.4.2.15 tf201" Came upon this, tried to flash twrp2.3.1.0 for the tf201 (downloaded straight from their website)... Still in 2.8.7.2 ... Okay, what? FINE! Screw it, redownload the stock ROM that got me into this mess (here) and see if I can even flash that. Wipe all the usual but internal storage because I'm lazy and afaik it doesn't need to be wiped anyway. Error: "E:Error executing updater binary in zip" The line above it, "symlink: some symlinks failed". Popped into here, unmounted the things, reformatted /data to f2fs (this may just be a Marshmallow thing though... it was ext_4 before I reformatted) Same error... Kill me.
So the problem as it stands now. I'm cannot seem to flash a different custom recovery and whenever I try to flash a ROM I get "E:Error executing updater binary in zip" The line above it, "symlink: some symlinks failed". I give up for now... Maybe I'll try again tonight. I'm running bootloader 10.4.2.15 and TWRP KANG 2.8.7.2 (which seems to require a 14.10 bootloader). In this mess, I don't know what to fix nor how to fix it. The angles I see are fix the custom recovery or fix the error/symlink problem since the bootloader version seems to be dependent on successfully flashing ROMs.
I'm sure there's someone out that that can point to me the correct tree in this forest using their superior knowledge of the subject. Having grown up with computers, even a new error message is something to work with. But when you can't even get results (success nor detailed failure), then it becomes downright no fun.
Hey everyone,
So! I bought a Sony Xperia 1 (J8110-2019) phone from someone on Facebook Marketplace at a very solid price of £250 (RRP is still £850 in the UK) due to the seller describing it as 'in retail demo mode' so they lowered the price. I jumped the gun thinking I was getting a solid deal and just stupidly assumed it to be a feature I could just disable with *#*#73556673*#*#- me believing I was some insane developer with mad coding skills where in realityI had once flashed and rooted my Xperia XZ back in 2016. [Insert 'Hackerman' meme]
Yes... I am fully aware I'm a complete idiot for not doing a full assessment on the phone and am now having to learn a very important lesson from this situation!!
It seems to have a Store Front firmware installed and unsure what firmware to download and flash? I've tried some of the official stock ROMs from XperiFirm and it just continues to boot into constant 10-second cycles of demo videos making general functionality like phone calls pretty much impossible. without interruption. I've tried Customized and UK Service Provider Firmware such as EE and O2 but it always goes back into Store mode.
I was hoping if anyone would have or could elaborate on how to make an executable system flash zip for a 2019 Xperia 1? When I extract files from XperiaFirm ROMS (FTF,ZIP,SIN etc), I don't seem to get any META-INF files and thus cant make the proper .zip that TWRP needs to successfully flash a new repacked stock ROM? It always ends in a boot loop."
Here are some key points to hopefully give you some background:
I've installed TWRP successfully and have attempted to use 3 official firmware to flash whilst in recovery but have been unsuccessful each time with 'Invalid .ZIP format'. I've only a few times got booted whilst bundling together FTF files via Flashtool and doing it that way round but only ever seems to solve half the problem
I can't use the SinExtract feature in Flashtools as the SIN file errors as not being supported yet to use different file versions.
I can't use PRFCreator as it errors as the FTF file being unsupported (Due to it being new I assume)
I attempted to create my own META-INF>Updater-script but am unable to identify what partition my phone would use for mounting on "/dev/block". I only ever seem to get MANIFEST.MF from the files and nothing else. On my XZ I think I used something like:
(package_extract_file("boot.img", "/dev/block/mmcblk0");
package_extract_file("system.sin","/dev/block/platform/msm_sdcc.1/by-name/system");
Click to expand...
Click to collapse
I have been able to install Magisk for rooting and verified.
I have used Minimal ADB and Fastboot to install programs like TWRP, SuperSu, Magisk but have never attempted, nor would I even know how to wipe my phone completely and install a clean stock ROM - is this possible?
All drivers, software, and systems are correct and up to date (as far as I am aware)
Would installing the' Service Exchange Firmware' be recommended (if I ever make it that far!) due to it being StoreFront?
I checked the IMEI number to see if it was blacklisted/blocked and it's all good. Not lost or stolen.
Thank you for your time to read and wallow in my woes with me my lovelies! Any help would be GREATLY appreciated you magnificent beasts! x
Bump x
...
the last chance... :good: