Related
Ive tried to s-off my Wildfire like 3 times. The first one i failed cz i chose HBOOT 1.01.0001. The second one it was stucked on Acquiring Root <method 1> then i waited, then it said click anything to exit. after that my third times, it doesnt detect my handset.
Does it mean my WF already s-off or what?
Thanks a lot to who has answered my question
You can check the HBOOT version by pressing Vol - and power when turning it on.
i already know its 1.01.0002
But then when i tried to do it again, the alpharevx doesnt detect my phone. it only said : Android
Then it wanted i put the serial
nvm, it detects now. But it stucks when it says Thank you for participating
hye...
i am rlly new with this forum just rcently bcame a mmber... n of cz vry noob...
i hving this problem when i try to run the alpharev X it says waiting for device..
so?? what had i done wrong i already know that my HBOOT is 1.01.002..
btw sory my english..
Did you set your phone at USB-debug and charge only?
how to enable the USB debug?? i hve set myphone to chrge only still alpharex doesnt detect myphone..
USB debugging is under Settings->Applications->Development
does it take a long time for the alpharev X to dtect the phone cz i follow all ur instructions it still shows waiting for device..
ss_sk said:
does it take a long time for the alpharev X to dtect the phone cz i follow all ur instructions it still shows waiting for device..
Click to expand...
Click to collapse
No. It detects it almost immediately. Possible solutions:
- Make sure USB Debugging is On, as already said above
- Redownload the AlphaRev X Executable file
- Make sure Drivers are installed and working properly. There are 2 aspects to this:
1) Install HTC Sync, and, Uninstall it. The ADB Drivers will be installed
2) The HBoot Drivers are next. Guide to install that is here:
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
i try to install the hboot driver .. i follow the steps but i get stuck cz i cannot find C:/android-sdk-windows/usb driver to install the diver...
ss_sk said:
i try to install the hboot driver .. i follow the steps but i get stuck cz i cannot find C:/android-sdk-windows/usb driver to install the diver...
Click to expand...
Click to collapse
Its an example. The actual file will be the one you downloaded. (Theres a link in the first line of that guide called Unrevoked Modified USB Driver)
thanks i just install the hboot driver.. install htc sync and uninstall htc sync.. so now i hope alpharev x can detect my phone... again thank u 4 the help..
now rise another problem.. alpharev x can detect myphone but when i enter the beta key base my serial no it says invalid beta key...
im pretty sure i enter the right serial key and the right beta key..
ss_sk said:
now rise another problem.. alpharev x can detect myphone but when i enter the beta key base my serial no it says invalid beta key...
im pretty sure i enter the right serial key and the right beta key..
Click to expand...
Click to collapse
Redownload the alpharev zip and run it, worked for me.
Hmmm which rom to test getting bored of cm7
Sent from my HTC Wildfire using XDA Premium App
There are two possible solutions there again. But, before that, make sure you have entered the right details (Right Serial Number (HT0....), Right HBoot Version, Right Device Model).
Once you are sure these are correct:
- Solution 1 - Copy the beta key in your clipboard from the website, then right click the title bar of the AlphaRevX Application, Click Properties, then check mark Quick Edit Mode. Then Right click anywhere inside the window, it will paste the key.
- Solution 2 - Redownload the AlphaRevX Application from the website and retry.
EDIT: Ninja'ed, Oh well.
lol sory mymistake... actually i really put the wrong beta key...
now that i hve S-OFF myphone what should i do now... sorry i really dont know anything..
Two ways again:
1) Follow this guide:
http://forum.xda-developers.com/showthread.php?t=1130044
2) Use Fastboot (Which I used)
- Download Android SDK - http://developer.android.com/sdk/index.html
- Download ClockworkMod Recovery - http://forum.xda-developers.com/show....php?t=1014498
- Extract the Recovery.img file from the 2nd link, and place it in your SDK Setup Path / Tools (eg: C:/android-sdk-windows/tools)
- Open a Command Window (cmd)
- Browse to the tools folder in this Command Window
- Type the command fastboot flash recovery recovery.img
- It will install ClockworkMod Recovery, you are done.
Then, simply follow Part 3 of this guide to install Custom ROMs and Stuff, irrespective of what you followed above.
http://forum.xda-developers.com/showthread.php?t=824396
i hve download the sdk there are 2 package android-sdk_r11-windows.zip and installer_r11-windows.exe..
so which one should i run??
i dont understand this part [- Extract the Recovery.img file from the 2nd link, and place it in your SDK Setup Path / Tools (eg: C:/android-sdk-windows/tools)]
ss_sk said:
i hve download the sdk there are 2 package android-sdk_r11-windows.zip and installer_r11-windows.exe..
so which one should i run??
i dont understand this part [- Extract the Recovery.img file from the 2nd link, and place it in your SDK Setup Path / Tools (eg: C:/android-sdk-windows/tools)]
Click to expand...
Click to collapse
EXE File.
That post simply means, that when you have completed installing your SDK, then, there will be a folder called "Tools" at your install location. Copy Paste the Recovery.img file to the Tools folder.
ok now i hve copy the recovery.img into tools
then open cmd right?? now what??
Hello. I have 2 questions.
1. > What is difference between stock radio [5.xxx] & newest radio [32.xxx] ?
2. > How can i flash radio with DATA++ hboot.
THX!
sry 4my bad english...
zingga said:
Hello. I have 2 questions.
1. > What is difference between stock radio [5.xxx] & newest radio [32.xxx] ?
2. > How can i flash radio with DATA++ hboot.
THX!
sry 4my bad english...
Click to expand...
Click to collapse
It seems you know about radios, so I reckon you know about AdamG radio thread. Cared to read the first post with understanding?
zingga said:
Hello. I have 2 questions.
1. > What is difference between stock radio [5.xxx] & newest radio [32.xxx] ?
2. > How can i flash radio with DATA++ hboot.
Click to expand...
Click to collapse
1. > the newest is 5.17.05.23, where did you even find 32.xxx?
2. > as you on data++ hboot - via fastboot only see alpharev.nl for explanation
kotag82 said:
the newest is 5.17.05.23, where did you even find 32.xxx?
...
Click to expand...
Click to collapse
The latest radio is 32.56.00.32U_5.17.05.23
All radios start with "32" but the number after the "U" is the important one.
weimar-zero
You can flash it via Android Debug Bridge (install ADB on your PC and the HTC driver from HTC Sync).
1. start your Desire in "fastboot-mode" (bootloader / fastboot)
2. You´ve to put the radio-file into the ADB folder (on your PC)
3. Change the name of the radio file in "radio.img"
4. connect PC to Desire via usb
5. make the test on ADB* (attached pic, input "adb devices" -> push enter!). If ADB works you´ll see the serial number of your Desire.
6. ADB input on Windows CMD* to flash the radio "fastboot flash radio radio.img" -> push enter!
*you´ve to go to the ADB Folder with CMD
regards weimar-zero
as always, no guarantees, everything on your own risk
Weimar-zero said:
You can flash it via Android Debug Bridge (install ADB on your PC and the HTC driver from HTC Sync).
1. start your Desire in "fastboot-mode" (bootloader / fastboot)
2. You´ve to put the radio-file into the ADB folder (on your PC)
3. Change the name of the radio file in "radio.img"
4. connect PC to Desire via usb
5. make the test on ADB (attached pic "adb devices"). If ADB works you´ll see the serial number of your Desire.
6. ADB input on Windows CMD* to flash the radio "fastboot flash radio radio.img" -> push enter!
*you´ve to go to the ADB Folder with CMD
regards weimar-zero
as always, no guarantees, everything in your risk
Click to expand...
Click to collapse
You made some big mistakes in your guide:
Radios do not get flashed via ADB, they get flashed via fastboot. And for this is:
1. Fastboot needed (extract file to C:\android-sdk), which is not included in newest SDK
2. Phone needs to be in Fastboot mode, not ADB mode: Turn phone off, press and hold Back + Power Button until FASTBOOT in red higlighted capital letters appears.
Now connect phone to computer via USB (FASTBOOT USB should appear). Then start CMD and change to android-sdk-folder
Code:
cd C:\android-sdk
Now enter
Code:
fastboot devices
Output should show be
Code:
List of devices attached
HTXXXXXXXX device
The "XXXXXXXX" are placeholde for a number (that's your phone's serial number).
If you get this kind of output: download the radio you want to flash as zip. THEN DO NOT RENAME IT!!!. Extract it and copy the radio.img to C:\.
Then enter in CMD the following command
Code:
fastboot flash radio radio.img
.
Now drink a cup of tea/coffee and wait until the process is done.
For an easier flashing process I recommend to use Android Flasher (read carefull before using):
http://forum.xda-developers.com/showthread.php?t=794638
Thank you MatDrOiD,
Your right, you don´t have to rename it, because in the zip the file has the name "radio.img"
Step 3 is not necessary
I did it on this way and it works pretty fine.
@MatDrOiD please tell me my big mistakes in the guide
You've just described in the same way, but just a bit more readable
ps: "ADB mode", what is this? I've never heard.
regards weimar-zero
Weimar-zero said:
Thank you MatDrOiD,
Your right, you don´t have to rename it, because in the zip the file has the name "radio.img"
Step 3 is not necessary
I did it on this way and it works pretty fine.
@MatDrOiD please tell me my big mistakes in the guide
You've just described in the same way, but just a bit more readable
ps: "ADB mode", what is this? I've never heard.
regards weimar-zero
Click to expand...
Click to collapse
IMHO these two mistakes are big ones (descending order):
1.) Telling the OP to rename the file. Reason: If something gets wrong in the process of Radio flashing, the Phone might be completely bricked!
2.) Telling the OP to use ADB, which does not work in Fastboot-mode, in which the Phone has to be. As already mentionend, Radio-flashing is a very sensitive process, all advices should be correct.
To understand what ADB / Fastboot are and what their difference is, I recommend you to read the guide in my signature about it. Would make me happy, if you tell me afterwars, wether you understand everything.
Thanks matdroid 4 info. But i don't see answer on 2nd questions?
So was diffirence between latest & others radios?
Is it difference just in FMradio like in app?
thanks
Updating Radio means updating your hardware. This can cause good things (better signal, battery life), but also the opposite. Radios are not good in general. Some users deal with this one, some with others.
For what its worth my advice to OP would be if current radio works fine with Rom then leave well alone, anything goes wrong with radio flash = proper brick
Sent from my HTC Desire using Tapatalk 2
Extracting ROM files from HTC RUU
Official HTC ROM updates are released as RUU (ROM Update Utility), which you run on your (Windows) PC to get the target device updated automatically.
Some of the big brains in the Android community release RUUs re-packaged into signed update files,
which in turn allow for whatever ROM customization you can imagine.
In this how to I will explain how to extract ROM files from a RUU image,
which you can then customize and use to flash your device without the fear of a new bootloader possibly making your device unrootable.
Requirements :
Windows PC,
Microsoft Process Monitor,
File Archiver capable of extracting ZIP files(eg, 7ZIP),
Official HTC RUU for your Android device.
The process of extracting ROM files from a RUU is really straightforward.
The idea behind it is that the self-contained update utility first needs to unpack the update payload into a temporary folder before pushing it onto the device.
This is when we grab the ROM file...
1. download the official RUU
2. start Process Monitor.
3. press CTRL+L
4. change "Architecture" to "Process Name"
5. leave the "is" field as it is
6. in the empty field copy and paste the name of your
RUU file (eg, RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed.exe)
7. click "Add"
8. change "Process Name" to "Path"
9. change "is" to "Contains"
10. in the blank field type "rom.zip" (without quotes)
11. click add
Click "OK" to set the filter and then run the RUU file.
Once the utility starts switch back to Process Monitor and look for an entry in the "Path" column that ends with "\rom.zip".
Right click on that line and select "Jump to..."
this will open a Windows Explorer window in the folder which contains the zipped ROM files
Copy the "rom.zip" file to some other folder, outside of the temp RUU folder tree (eg, desktop)
Once copied, close Process Monitor and the RUU utility.
The copied "rom.zip" file contains the following files:
android-info.txt - list of CIDs this RUU will flash to,
boot.img - root file system image,
hboot (followed by a version string) - boot-loader update,
radio.img - radio driver update,
recovery.img - recovery partition image,
splash1_Hero_320x480.nb0 - boot loader splash image,
system_rel.img - system partition image,
userdata.img - data partition image.
You can now, among many other things, root the ROM
and then flash the updated boot.img and all the other image files on to your device using Recovery
it doesnt work... the process monitor colum is all blank after running RUU... there are no processes listed
munnibhai said:
it doesnt work... the process monitor colum is all blank after running RUU... there are no processes listed
Click to expand...
Click to collapse
you mst be doing something wrong i double checked the method and it still works fine for me..
make sure your environment is set up correctly and run everything as administrator or disadle uac in windows..
thanks for the reply, let me check it again...
i will post back to u
rom.zip corrupted
I followed the directions and like another post in here procmon shows a blank screen. I went to task manager and opened processes and saw when it ran then clicked open file location and found it. I did this twice and both zips are corrupt. (used winzip)
error [D:\android apps\EVO root\EVO\rom.zip]: start of central directory not found; Zip file corrupt.
Possible cause: file transfer error
when I close the RUU all the files in that folder disappear so you have to leave the RUU running while you copy the zip file or it's gone.
At least that's what I saw.
update to last post
I found a zip repair tool and was able to repair and extract the 1.10.653.2 RUU rom capture. I will have to try to run it later. If anyone gets corrupted zip error, Zip Repair pro will repair it.
To get the rom zip without any errors just run the ruu.exe file, when the box with a picture of a phone pops up, click start on pc, type in "run" and click on run then in that box that pops up, type in %temp% and click ok. Another window pops up then just scroll down to the most recent folder and rom.zip will be in there, if not it will be in the next folder.
Hi,
when I try to open the rom.zip I get an error message, it just said it cannot open with 7zip and with windows it says its invalid.
I tried downloading the RUU multiple times but still the same error. I rune the RUU as administrator.
Tried copying it over to different locations and then open it.
RUU_ENRC2B_U_JB_45_O2_UK_1.14.206.13_Radio_3.1204.167.31_release_289474_signed
HTC ONE X+
Thank you
Update:
I used Zip Repair Pro.. however there is no boot.img inside the repaired zip -_-
For those which have problem with making Process Monitor detect RUU temp folder, make sure You add whole file name of RUU including .exe at the end.
Jmcclue's steps, work perfectly, Thank you post #7
htc RUU Rom
Inside 4ndroid said:
Extracting ROM files from HTC RUU
Official HTC ROM updates are released as RUU (ROM Update Utility), which you run on your (Windows) PC to get the target device updated automatically.
Some of the big brains in the Android community release RUUs re-packaged into signed update files,
which in turn allow for whatever ROM customization you can imagine.
In this how to I will explain how to extract ROM files from a RUU image,
which you can then customize and use to flash your device without the fear of a new bootloader possibly making your device unrootable.
Requirements :
Windows PC,
Microsoft Process Monitor,
File Archiver capable of extracting ZIP files(eg, 7ZIP),
Official HTC RUU for your Android device.
The process of extracting ROM files from a RUU is really straightforward.
The idea behind it is that the self-contained update utility first needs to unpack the update payload into a temporary folder before pushing it onto the device.
This is when we grab the ROM file...
1. download the official RUU
2. start Process Monitor.
3. press CTRL+L
4. change "Architecture" to "Process Name"
5. leave the "is" field as it is
6. in the empty field copy and paste the name of your
RUU file (eg, RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed.exe)
7. click "Add"
8. change "Process Name" to "Path"
9. change "is" to "Contains"
10. in the blank field type "rom.zip" (without quotes)
11. click add
Click "OK" to set the filter and then run the RUU file.
Once the utility starts switch back to Process Monitor and look for an entry in the "Path" column that ends with "\rom.zip".
Right click on that line and select "Jump to..."
this will open a Windows Explorer window in the folder which contains the zipped ROM files
Copy the "rom.zip" file to some other folder, outside of the temp RUU folder tree (eg, desktop)
Once copied, close Process Monitor and the RUU utility.
The copied "rom.zip" file contains the following files:
android-info.txt - list of CIDs this RUU will flash to,
boot.img - root file system image,
hboot (followed by a version string) - boot-loader update,
radio.img - radio driver update,
recovery.img - recovery partition image,
splash1_Hero_320x480.nb0 - boot loader splash image,
system_rel.img - system partition image,
userdata.img - data partition image.
You can now, among many other things, root the ROM
and then flash the updated boot.img and all the other image files on to your device using Recovery
Click to expand...
Click to collapse
this is good working 100% thank you :good:
i_4_u89 said:
this is good working 100% thank you :good:
Click to expand...
Click to collapse
no problem and please instead of saying thanks please remember to hit the thanks button on threads first post..
works great, to bad you cant open the zip file
jpwhre said:
works great, to bad you cant open the zip file
Click to expand...
Click to collapse
You can open the zip. Go back a page n try the way i said.
jmcclue said:
You can open the zip. Go back a page n try the way i said.
Click to expand...
Click to collapse
note path is desktop (last post showed from temp folder) and i still get same results. did some searching and aperantly htc now signs their zip files and they can't be opened anymore. having usb issues that causes fastboot force close errors and need to be able to flash boot.img thru flashify app to return it to stock. ran the htcguru reset rom that uses aroma installer to return to stock that lets me take ota's but i get qualcom location force close and other custom roms give me issues forcing me to reset phone to stock every few days with guru installer. flashing recovery in fastboot is a chore as well. I have s-off and can keep it, but doing fastboot oem lock wont relock the bootloader, even though it shows success in cmd line. i can cid and super cid with fastboot.
it leaves me at a point where i really need to pull everything out of the rom.zip file and it wont open.
pic 1, 7zip wont open archive on desktop
pic 2, how i get recovery to flash
pic 3, results from running RUU
i have to reboot device, set comand to reboot bootloader, set command to flash recovery all faster than phone will do all commands to get it to flash, and RUU doesnt work that fast. i know im on sprint with htc one m7, but google search "extract htc zip" "extract rom.zip" both lead to this thread as top result. no other searches will tell me how to open the archive, except one that resulted in "htc signed zips can no longer be opened"
you're more than welcome to give it a go
http://forum.xda-developers.com/showthread.php?t=2795856 Sprint_HTC_One_m7wls_5.05.651.2_RUU.exe
Did HTC change the way they create the exe? I don't find it, the biggest file is data1.cab file that I can't extract.
I'm trying to extract the stock rom for an ATT HTC One Mini (m4) because RUU keeps crashing on me and won't install. I am also rooted with S-off.
If anybody can help me get the stock m4 rom so I can go back to stock, I would really appreciate it.
SyPete said:
Did HTC change the way they create the exe? I don't find it, the biggest file is data1.cab file that I can't extract.
I'm trying to extract the stock rom for an ATT HTC One Mini (m4) because RUU keeps crashing on me and won't install. I am also rooted with S-off.
If anybody can help me get the stock m4 rom so I can go back to stock, I would really appreciate it.
Click to expand...
Click to collapse
No they didn't change it. Some ruu's use a different format requiring the use of a tool called unruu instead of trying to capture the zip file when using the exe (I just learned this today). I've gone ahead and used unruu and the resulting zips have been put in a single tar file. you can download it from here for about 30 days after which ill have to delete the file. also i dont know which zip has what in it.
hi
master how to open Zip firmware !!?
i want to open zip firmware (PM60IMG.zip Desire 400)with 7zip ! but shows below error :
"can not open file PM60IMG.zip az archive "
how to pass this encryption ?
gandolf007 said:
hi
master how to open Zip firmware !!?
i want to open zip firmware (PM60IMG.zip Desire 400)with 7zip ! but shows below error :
"can not open file PM60IMG.zip az archive "
how to pass this encryption ?
Click to expand...
Click to collapse
https://github.com/kmdm/ruuveal/tree/f4936338f19841c75edafbe7e622242105cb39aa
Splash Screen Creation!!!
-Windows instructions-
I have unlocked bootloader and S-OFF. (The attached android-info.txt is for the INTERNATIONAL Variant only)
Video linked at the bottom to follow along with, if the words here are too hard to follow...
per usual, not responsible for bone-headed ness
You will need:
latest adb & fastboot
benny3's Image Converter (extracted in a project folder)
an image in the dimensions of 1080x1920 (can be .png, .jpg, .bmp)
latest View attachment android-info.txt
**optionally** Photoshop, GIMP, Paint (I guess this could work. eek)
Steps to make your HTC One not blind you upon a restart...
Edit photo to liking
MAKE SURE IMAGE IS THE CORRECT SIZE ---> [ 1080x1920 ] <---
Open benny3's converter FOLDER, copy image to the 'place-image-here' folder
Run CLICK-HERE.BAT
Convert .jpg (.bmp, .png) to .img, close upon completion
Copy custom.img(from place-image-here folder) to Project Folder, rename file to splash1.nb0
Copy android-info.txt to same Project Folder
Zip/Archive these two files (I use winRAR), archive format MUST be .zip
Copy ProjectFolder.zip to sdk directory (wherever your fastboot command is located)
Reboot into Download Mode, plug phone into computer
Open adb/fastboot folder in command prompt (SHIFT + Right-click inside folder)
Code:
fastboot devices
fastboot oem rebootRUU
fastboot flash zip ProjectFolder.zip
fastboot reboot
Enjoy
Video to follow along with...
https://youtu.be/EpxvJozVB2U
-MAC OSX instructions-
http://forum.xda-developers.com/showpost.php?p=60823528&postcount=5
Thanks to @schmeggy929, @SoLdieR9312, @benny3 for the tool and the community for the information :good::good:
Link to some splash screens I've made coming soon (may/may not takes requests), meanwhile,
check out [MOD][S-OFF] Splash Screen Collection for HTC One M9by @SoLdieR9312
Will that latest info.text run on a verizon variant running build 1.33.605.15? I get errors and failed messages on anything else.
Archangel said:
Will that latest info.text run on a verizon variant running build 1.33.605.15? I get errors and failed messages on anything else.
Click to expand...
Click to collapse
If you do a "fastboot getvar all", do you get:
Code:
MID: 0PJA30000
CID: VZW__001
If so, I think those are the only differences between the android-info.txt for int, sprint, vzw, and so on...
If those are your values, try this. just rename to android-info.txt
Instructions for OSX
I'm adding instructions for anyone with a Mac who doesn't want to bother with Bootcamp, as Benny's tool is a Windows batch file. This is essentially the same process, just manually. (As stated above, you must of course be s-off.)
You need a utility called ffmpeg, which you can download here: http://ffmpegmac.net. Place the ffmpeg app in a separate folder (don't try to install it, just drop it there).
1. Prepare splash image and name custom.jpg
2. Move custom.jpg to ffmpeg folder.
3. Open Terminal at folder.
4. Enter this command:
Code:
./ffmpeg -i custom.jpg -f rawvideo -pix_fmt rgb565 splash1.nb0
This will output a splash image in that folder with the name splash1.nb0.
5. Using an archiving program (not the OSX Archive command, which will include extraneous files), zip the splash image and android-info.txt into a single zip file. I use B1FreeArchiver.
6. Flash in fastboot/Download mode as above.
I get errors and failed messages on anything else.
Worked perfect brother thank you!
predator1584 said:
If you do a "fastboot getvar all", do you get:
Code:
MID: 0PJA30000
CID: VZW__001
If so, I think those are the only differences between the android-info.txt for int, sprint, vzw, and so on...
If those are your values, try this. just rename to android-info.txt
Click to expand...
Click to collapse
I have132.401.17 can I still use the. 15 android txt file
acidspider said:
I have132.401.17 can I still use the. 15 android txt file
Click to expand...
Click to collapse
The only thing that matters, is the Model-ID and CID. If it doesn't work, it'll give you an error and shouldn't cause any issues, give it a whirl and let me know!
can flash in download mode?
fastboot flash filename.zip?
---------- Post added at 05:43 PM ---------- Previous post was at 05:25 PM ----------
predator1584 said:
The only thing that matters, is the Model-ID and CID. If it doesn't work, it'll give you an error and shouldn't cause any issues, give it a whirl and let me know!
Click to expand...
Click to collapse
worked a treat, cheers
Made a nice M9 splash. made from the MultiCam theme from my old M8 Thanks to @rayford85, @Pfaffinator for the image. i just added some personal MERICA stuff.
works great on my M9 with the Viper one m9 2.2.0 with the 1.40.401.8 firmware.
Here is a pic of it.
https://www.dropbox.com/s/t746gf4jy25sj77/molon.jpg?dl=0
Semi-n00b here: Is there a way to extract the android-info.txt from my device via adb or root? I want to try this on my One M8, but I need the right android-info.txt, I can't download any stock firmwares online because Android File Host is currently down and that's where the only ones are currently being hosted. Sorry in advance if this is stupid, google really didn't give me any answers...
bryanedwards441 said:
Semi-n00b here: Is there a way to extract the android-info.txt from my device via adb or root? I want to try this on my One M8, but I need the right android-info.txt, I can't download any stock firmwares online because Android File Host is currently down and that's where the only ones are currently being hosted. Sorry in advance if this is stupid, google really didn't give me any answers...
Click to expand...
Click to collapse
There's no such thing as a Noob-question, but if you take the latest OTA or firmware update and extract the "android-info.txt" file, you can then put that file into the folder where you're creating the splash screen, I uploaded a video that shows just how easy it is once you have the "android-info.txt," if you have any more questions, feel free to message me. I'm always happy to help
Updated with more compatible adb link!
This is what I did to get the new beta. Feel free to tell me how dumb I am for allowing noobies to try the beta, but the more the merrier and they should know the risks....
RISKS: Phone may not be as stable as before and you will lose all your apps and data. Camera is bugged for me
1. BACK UP YOUR CURRENT BUILD USING SMART SWITCH. THIS WILL WIPE DALVIK/CACHE/DATA. Get SmartSwitch for PC HERE
2. Download Samsung Drivers for ADB/ODIN HERE
3. If you are on firmware ending in AUI5 for the CSC version XAA then skip to step #6 . If you are not, then download the respective firmware HERE
Also Download Patched ODIN (Patched version will be less scrutinous) HERE
4. Unzip the firmware you just downloaded as well as the Patched Odin. Run ODIN and add the BL, AP, CP, Home_CSC from the unzipped firmware to the corresponding locations in ODIN
5. Turn off phone and boot into "Download Mode" by first holding Volume +/- buttons and then hold the Power button. Now plug in your phone to your PC and you will see the first small grey square in the upper left side of ODIN turn light blue (if it does not, you have issues with either the cable or drivers).
Proceed in flashing the device by simply clicking the "Start" button.
Once it is done and your phone has rebooted... Make sure that you complete the setup process just in case of authentication issues if the phone isn't already set up
6. Download the OneUI 4 Beta HERE and then follow the guide to install adb https://www.xda-developers.com/install-adb-windows-macos-linux/
7. Follow the XDA adb install guide and make sure to allow adb systemwide when asked by the program.
8. Turn off phone. Boot into device by holding Volume Up and then holding Power. This will take you into recovery mode, where you will see the option to "update via ADB sideload".
Use the volume down key to navigate down to that option and press power to initiate the adb sideload function
9. Open command prompt by pressing the Windows key and typing "cmd" (no quotes) and press ENTER.
10. Type into the command prompt (of course remove the quotes) "adb sideload C:\path\to\your\oneui4\zip\file" . For example if I download that file into my Downloads folder, I would then type "adb sideload C:\Users\MyPC\Downloads\949981470b3948c3aa05a19e8a2edbd3.zip"
Bro I have SM-F926B, I downloaded the correct CSC but can't install the beta, I got a message on smd says can't read. Any help please?
shadi90 said:
Bro I have SM-F926B, I downloaded the correct CSC but can't install the beta, I got a message on smd says can't read. Any help please?
Click to expand...
Click to collapse
This is for US Fold 3 models f926U/1. Sorry brotha. Basically you need to change the beta file you downloaded to this http://fota-secure-dn.ospserver.net...48:16&px-unum=&px-nb=UGtezEZ854jbmFcvWGxLEA== as well as flash AUJ7 firmware first. I hear UK with CSC BTE works fine. Get it at https://samfw.com/firmware/SM-F926B/BTE/F926BXXU1AUJ7 . After you replaced those files, just follow the instructions again
Thanks for this Guide. But i have issue with Adb sideload update.zip
I downgrade to AUI5 and been using XAA firmware since i bought T-mobile Zfold3.
And since beta was released, I'd been trying to register for OneUI4 in Samsung Memeber app but No Banner or under rBenefit tab.
So saw your guide here and tried to followed your direction but adb sideload fails i get CANNOT READ message.
when i typed adb Devices it shows my device so adb is working but cannot sideload.
when i downloaded the update it was .bin 949981470b3948c3aa05a19e8a2edbd3.bin so i renamed it to .zip, i got the CANNOT READ message then renamed it to update.zip still the same Cannot Read.
I am using windows 11.
Haven't logged in to XDA in years. Just wanted to say THANK YOU.
mha1021 said:
Thanks for this Guide. But i have issue with Adb sideload update.zip
I downgrade to AUI5 and been using XAA firmware since i bought T-mobile Zfold3.
And since beta was released, I'd been trying to register for OneUI4 in Samsung Memeber app but No Banner or under rBenefit tab.
So saw your guide here and tried to followed your direction but adb sideload fails i get CANNOT READ message.
when i typed adb Devices it shows my device so adb is working but cannot sideload.
when i downloaded the update it was .bin 949981470b3948c3aa05a19e8a2edbd3.bin so i renamed it to .zip, i got the CANNOT READ message then renamed it to update.zip still the same Cannot Read.
I am using windows 11.
Click to expand...
Click to collapse
Don't rename the file.
What I always do with adb related stuff is put it in the root of my C drive. So it would be
Code:
C:\adb\platform-tools\
Then put the .bin file in here as well.
After that open cmd and do
Code:
cd C:\adb\platform-tools\
and hit enter.
After that do adb sideload 94 and hit tab so it should autofill the name of the update file.
Let me know if you have any questions.
Thanks for the instructions as they worked for me. I did receive an error before it finished at "(~94%) adb: failed to read command: No error". Phone booted and the system is showing One UI version 4.0, Android Version 12.
QUESTION though. What is up with the difference in Baseband version? I am seeing the official release having the last 2 digits of "JF" but on the phone just flashed, it is showing "JH".
For reference, complete Baseband version: F929U1UEU1ZUJH after flashing. Might just be my ignorance but thought I would ask.
Thoughts? And thank you again!
AlexMartin00 said:
Thanks for the instructions as they worked for me. I did receive an error before it finished at "(~94%) adb: failed to read command: No error". Phone booted and the system is showing One UI version 4.0, Android Version 12.
QUESTION though. What is up with the difference in Baseband version? I am seeing the official release having the last 2 digits of "JF" but on the phone just flashed, it is showing "JH".
For reference, complete Baseband version: F929U1UEU1ZUJH after flashing. Might just be my ignorance but thought I would ask.
Thoughts? And thank you again!
Click to expand...
Click to collapse
The baseband is just something that gets updated, so ZUJH is the Android 12 beta firmware. Every time you update your firmware the baseband gets updated as well.
More technical: Baseband is firmware that controls all radio devices on the phone, including GPS, Wi-Fi, Bluetooth, NFC, cellular data, and more.
Will this work on att Galaxy fold 3 since I can't get update cause att blocks it.
Hero_is_Over said:
This is what I did to get the new beta. Feel free to tell me how dumb I am for allowing noobies to try the beta, but the more the merrier and they should know the risks....
RISKS: Phone may not be as stable as before and you will lose all your apps and data. Camera is bugged for me
1. BACK UP YOUR CURRENT BUILD USING SMART SWITCH. THIS WILL WIPE DALVIK/CACHE/DATA. Get SmartSwitch for PC HERE
2. Download Samsung Drivers for ADB/ODIN HERE
3. If you are on firmware ending in AUI5 for the CSC version XAA then skip to step #6 . If you are not, then download the respective firmware HERE
Also Download Patched ODIN (Patched version will be less scrutinous) HERE
4. Unzip the firmware you just downloaded as well as the Patched Odin. Run ODIN and add the BL, AP, CP, Home_CSC from the unzipped firmware to the corresponding locations in ODIN
5. Turn off phone and boot into "Download Mode" by first holding Volume +/- buttons and then hold the Power button. Now plug in your phone to your PC and you will see the first small grey square in the upper left side of ODIN turn light blue (if it does not, you have issues with either the cable or drivers).
Proceed in flashing the device by simply clicking the "Start" button.
Once it is done and your phone has rebooted... Make sure that you complete the setup process just in case of authentication issues if the phone isn't already set up
6. Download the OneUI 4 Beta HERE and then download the "15 Second ADB Installer" HERE
7. Install the 15 second adb installer and make sure to allow adb systemwide when asked by the program.
8. Turn off phone. Boot into device by holding Volume Up and then holding Power. This will take you into recovery mode, where you will see the option to "update via ADB sideload".
Use the volume down key to navigate down to that option and press power to initiate the adb sideload function
9. Open command prompt by pressing the Windows key and typing "cmd" (no quotes) and press ENTER.
10. Type into the command prompt (of course remove the quotes) "adb sideload C:\path\to\your\oneui4\zip\file" . For example if I download that file into my Downloads folder, I would then type "adb sideload C:\Users\MyPC\Downloads\949981470b3948c3aa05a19e8a2edbd3.zip"
Click to expand...
Click to collapse
hi I'm getting a status 1 error with my sideload
erneyone said:
hi I'm getting a status 1 error with my sideload
Click to expand...
Click to collapse
What does the error say?
I keep getting cannot read '949981470b3948c3aa05a19e8a2edbd3.bin and I do have the file on my ADB folder which is on the C drive i don't know if it matter but I'm using a windows 11 laptop
zimgir124 said:
What does the error say?
Click to expand...
Click to collapse
Status 1
Is there a mirror for the beta download anywhere? It looks like the link isn't working for me.
ElGuyarc said:
I keep getting cannot read '949981470b3948c3aa05a19e8a2edbd3.bin and I do have the file on my ADB folder which is on the C drive i don't know if it matter but I'm using a windows 11 laptop
Click to expand...
Click to collapse
was getting the cannot read error too.. the problem is the outdated adb version installed from the 15 second adb link in the op
download this:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
Dick_Stickitinski said:
was getting the cannot read error too.. the problem is the outdated adb version installed from the 15 second adb link in the op
download this:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
Click to expand...
Click to collapse
thank you so much...
I updated my SM-F926U1 with the Beta 4 its really buggy for me
Just want to get my facts straight. Can I just flash back to non-beta ?
What will happen to my Beta status will I still be able to OTA update when the next beta comes out ?
I have updated this with the newer adb binary install guide. I use the latest binaries from Android Studio and add them to path manually so I didnt know the 15 second installer was that outdated
Also yes you can downgrade by flashing the AUI5 that I posted in the guide
Hero_is_Over said:
I have updated this with the newer adb binary install guide. I use the latest binaries from Android Studio and add them to path manually so I didnt know the 15 second installer was that outdated
Also yes you can downgrade by flashing the AUI5 that I posted in the guide
Click to expand...
Click to collapse
Is it a good idea to wipe my data when doing an downgrade like this ?
Hero_is_Over said:
I have updated this with the newer adb binary install guide. I use the latest binaries from Android Studio and add them to path manually so I didnt know the 15 second installer was that outdated
Also yes you can downgrade by flashing the AUI5 that I posted in the guide
Click to expand...
Click to collapse
I thought you can't flash a previous version of Android once you're on the higher version?