{
"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"
}
With the autoloaders for the BlackBerry Priv now available for download, there's sure to be folks needing to know how the whole process works, and we're glad to help with that. Take a look at our full run down of how to reinstall the OS on your BlackBerry Priv. It's all fairly easy, but do keep in mind you will need to have a Windows or Mac computer to complete the process plus, reinstalling the OS will indeed erase all local data.
Overview
* Install the USB drivers for the Priv. To install the Priv drivers, click here.
* Download the autoloader file for your Priv version from the following URL: AT&T, T-Mobile USA, Verizon, Non US Carrier - STV100-1, STV100-3, STV100-4
* Press and hold both the Power and Volume Down buttons for 30 seconds to boot the Priv into fastboot mode. Alternatively, press and hold the Volume Down while turning on Priv and selecting Reboot into fastboot (when in fastboot mode, the Priv will display the BlackBerry Bootloader Menu and a purple LED)
Windows
* Open and extract the downloaded autoloader file (including all files and folders)
* Open the extracted folder
* Execute the flashall.bat
* Follow on screen instructions as prompted
Mac OS X
* Open and extract the autoloader file (note the location of the downloaded autoloader file (example: Documents, Downloads, Desktop)
* Rename extracted folder to Priv
* Open Terminal (Finder > Applications > Utilities > Terminal)
* Type cd /Priv
* Type ./flashall.sh and press Enter
Follow on screen instructions as prompted
Note: Completing the reload of the OS will erase all local data from the Priv.
Once completed, you should have a fully wiped device and be able to start entirely fresh with the setup process of your Priv. If you run into any issues, be sure to head on into the CrackBerry BlackBerry Priv forums to get some further help. And as always, you use these files at your own risk, don't blame us if you break things.
(Please note the above article is taken from Crackberry.com website:
How to reload the OS on your BlackBerry Priv | CrackBerry.com
http://crackberry.com/how-to-reload-the-os-on-your-blackberry-priv)
Can I flash "Non US Carrier" ROM on a AT&T Priv?
lacordaire01 said:
Can I flash "Non US Carrier" ROM on a AT&T Priv?
Click to expand...
Click to collapse
Did you try? I have the T-Mobile variant and it has way too much bloatware on it.
Crimson Ghoul said:
Did you try? I have the T-Mobile variant and it has way too much bloatware on it.
Click to expand...
Click to collapse
I tried, but the phone does not start after flashing it with Unbranded ROM... stuck in boot loader menu. I tried some combinations of files too but nothing worked.
Now I'd flashed the AT&T ROM again and the phone is working as before.
I tried but my priv got stuck in bootloader menu. any idea why?
Related
Hi I noticed allot of people asking for serials and or mirrors so I thought I would post one for you.
Download: http://www.megaupload.com/?d=JVQ62A39
Installation Instructions:
Note: This update is not intended for use on T-Mobile(US) HTC HD2, and doing so may have undesired side effects.
ROM Version:
Norway: 3.14.409.2, Spain: 3.14.412.2, Portugal: 3.14.410.2, France: 3.14.406.2, Sweden: 3.14.413.2, English: 3.14.405.2
Improved Functions:
1. This upgrade for HTC HD2 includes all previously released updates.
2. For the Contacts application allowing for faster searching and locating contacts.
3. Enhanced handling for CPU processing that will quicken the background processes allowing for an overall improved experience.
Before you proceed, please confirm that this software upgrade is a newer version than what is currently installed on your device. If it is the same version and your device is operating normally, there is no need to reinstall the software.
To check what version is installed on your device, click Start > Settings > System tab > Device Information > Version tab, and note the ROM version, CPU, and Radio version.
Warning!
* This is a generic software update. Any additional software or settings provided by your mobile operator or company will be lost. If you require this customization, please contact your supplier first before upgrading.
* Please note that this upgrade will erase any data stored on the device. Once you proceed with the upgrade, the system can not be downgraded again.
* Please back up your data first before upgrading your device. Before you run the ROM Upgrade Utility (RUU), make sure you check and do the following:
* The USB sync cable is connected to your device and PC. If your PC is running Windows XP®, ActiveSync® will run automatically to establish a connection. If your PC is running Windows Vista™, then Windows Mobile Device Center will establish the connection between your device and PC.
* All running applications on the device have been closed.
* Make sure that the battery level of the device is at least 50%. To check, tap Start > Settings > System tab > Power.
* The update will take up to 30 minutes, DO NOT interrupt the update process, make/receive phone calls, disconnect the device from the PC, or press any buttons until the process has been completed.
Once the RUU is downloaded, launch the application on your PC and follow the instructions.
* Click View Readme when executing the ROM Upgrade Utility (RUU) to view detailed upgrade procedure, error message information or Q&A
{
"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"
}
Download: http://www.megaupload.com/?d=JVQ62A39
thnx for the link.
question: can we downgrade with hspl after this upgrade?
Yes but I think flashing back to stock erases HSPL, so you would need to flash it back or use SSPL.
i got the curropted file error
download 3 times!!
seems your upload contained errors
Download is fine, you will just need to disable any download managers and just save the file
Failure
trying to install and upgrade to this rom after 1% and error message appears as follows
error 294 invalid vender ID
????????????????
Several threads already exist on the subject.
Hello.
At the beginning I want to say that English isn’t my primary language and I apologize for mistakes. I hope this text will be understandable.
I have problem with my LG P710 [L7 II].
Few months ago I have tried to upgrade it using LG_KDZ_FW-Update.
I have started to look for the best software for me and after a long time I found software which include root and CWM Recovery… wow.
Instalation wasn’t completed successfuly. From this time I can run my device only in Emergency Mode. No matter if I connect it to the USB, battery charger or just press button to turn it on.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I don’t know I did something wrong, the instruction was bad or maybe soft was demaged.
I have another cell phone so it wasn’t urgent to repair it then, but now I think it’s time to do it!
I hope you can help me with that.
I’m trying to do it this way:
• Download and install drivers [LGMobileDriver_WHQL_Ver_4.0.3]
• Download and install update tool [LG_KDZ_FW-Update_OfflineFix]
• Download software [V20A_00.kdz]
(I’m working on Lenovo G510 with Windows 10 installed)
• Change hosts file [C:\Windows\system32\drivers\etc] by adding at the end:
127.0.0.1 csmg.lgmobile.com
• Install B2CApp [setup file is inside LG KDZ FW Uptede Toll folder]
• Then I’m opening Automatic Offline Procedure script.
• Few windows appears on my screen. At this time I have Windows Enabler On and Small Server is running.
• After that script starts R&D test toll, I set Phone Mode [Emergency], select my .kdz file and
press Normal Web upgrade test, then on next window Upgrade Start.
• Afterward I clear Software Update Registry, select my language and press on OK.
• Phone Update window appears. Analysis done, download as well, but update stops at 4%.
According to the instruction I disconnect mobile, remove battery and connect it again with pressing Vol- (In order to enter Emergency Mode I guess. I’m lucky guy, I haven’t to press anything, my phone always turn on into Emergency)
• No change after clicking restart. 4% is everything I can get.
ctrlv.it/id/2452/3915649230 - Logs
If you know what is wrong, you have any advice, please help.
I'm 63 years old & could do with some help - trying to flash my Moto G4 but no luck
Hello folks.
I apologise in advance. I thought something was a good idea, and I said to myself I would give it a try and I won't give up, but I have been at this for about 5 hours now and no progress.
I have a Moto G4 which my wife gave about a year ago. I don't like stock Android and want to install Lineage OS onto it. I understand that first I need to:
1. Unlock my bootloader (done)
2. Install ADB Driver Installer onto my Dell (done)
3. Install Minimal ADB and Fastboot onto my Dell (done)
4. Plug my G4 into my Dell using the correct cable. It seems to work as the ADP Driver Installer / APK Installer recognises it as per the image below
/https://imgur.com/a/NBfrIcZ
5. Open up the command promt in the Minimal ADB and Fastboot folder, type adb devices - the device is recognised
6. Here is where the problems start!
(a) At this stage, as soon as I type adb reboot bootloader, the G4 reboots but as it does so it disappears from the ADB Diver Installer / APK Installer
(b) Soon after when I type fastboot flash recovery twrp.img then nothing is found, no files or directory or anything. I don't understand what I am doing wrong and am very stuck sadly
{
"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"
}
Would really appreciate some help!
Great, my pictures don't work. I don't understand why. But basically when I write fastboot flash recovery twrp.img (it is in the same folder as Minimal ADB and Fastboot), it says not found to a bunch of things and no such file or directory.
George425 said:
Great, my pictures don't work. I don't understand why. But basically when I write fastboot flash recovery twrp.img (it is in the same folder as Minimal ADB and Fastboot), it says not found to a bunch of things and no such file or directory.
Click to expand...
Click to collapse
Ask your question here in moto g4 forum you will gets answers correctly ,because that's where you should have asked, buts it OK here is the link https://forum.xda-developers.com/mo...hread-question-noob-friendly-t3526598/page175
And upload the photos in Google drive and turn on the link sharing feature and post the link there there are many people there to help you out. Don't worry, everything will be fine.
Thank you Dhanush-raj I will do that now.
Credit goes to:
@☆KØŁØЯΛĐØ☆ providing some of the device files + the original guide for another j737p variant this was modified from + testing/porting aforementioned root method
@topjohnwu for Magisk as always !!!
The link below is to the thread for the guide to root the j737p J737PVPU1ARG3 variant in which I modified this guide from.
https://forum.xda-developers.com/galaxy-j7/development/twrp-root-galaxy-j7-refine-8-0-boost-t3916575
------------------------------------------
Download all files needed as well as this guide saved to a .txt document here:
https://www.mediafire.com/download/uckb1mji1r01f9m
------------------------------------------
Read all before just winging it and follow directions with precision !!!
( Run all progams by right click - Run as administrator )
Step 1
Unzip - Odin3_v3.13.1 ( non-patched ).zip + Install the samsung USB drivers via SAMSUNG_USB_Driver_for_Mobile_Phones.exe
YOU MUST PAY ATTENTION TO THE FOLLOWING
- In the Step_1.zip you extracted, load up Odin_v13.1 (non-patched)
- Load only the BL/AP/CP files from your stock firmware into Odin
- As soon as the flashing process ends, you must reboot quickly back into Download Mode. You have to be quick. If you allow the device to begin booting up, it makes the rooting process more difficult.
Step 2
Assuming you followed directions...
- Close Odin_v13.1 & unplug your device while still remaining in Download Mode
- Launch Odin_v13.1 [Patched] & load up the patched_boot.tar in the AP slot
- Reconnect device & proceed to flash
- Device will reboot with "Verification Failure" so you must reset (this is part of root) (it does not activate FRP lock)
( It may get stuck at a soft bootloop on the samsung logo, if it does just hold the power button and volume down until it reboots again then let go. ) ( should not have to repeat this more than once or twice )
- When device reboots to Setup Wizard, skip through it. Do not add any accounts (Google or Samsung). Do not consent to giving any device data for whatever purposes (they will ask twice; look carefully)
- On the home screen, Go to settings - unlock Dev Options & allow USB Debugging. OEM should already have been unlocked.
Step 3
- Connect device to your pc & in the platform-tools+Magisk folder you, run CMD.exe
- Input adb devices to ensure proper connection
- Input adb install -r MagiskManager-v7.0.0.apk to install MM to your device
- Open MagiskManager & make sure everything is good to go (see attached screenshot)
- If everything is done properly then you will see a superuser tab in the left side-bar, indicating root access
ĐØΠΞ
Again many thanks to:
@☆KØŁØЯΛĐØ☆ - for the Original tutorial and testing via another j737p variant.
@topjohnwu - for Magisk
and credit to Vyp3r ( Myself ) @fsceo - for the files pertaining to this variant and modification of the original tutorial.
{
"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"
}
Would this work to root my SM-J737P with firmware J737PVPS9BUD2 on Android 9.0? What other files do I need to accomplish this? Thanks!
I DO NOT TAKE RESPONSIBILITY FOR YOUR DEVICE BREAKING
THIS /WILL/ COPY YOUR BOOTLOADER FROM ONE SLOT TO ANOTHER
IF YOU DO THAT WITH A BOOTLOADER THAT IS OLDER THAN THE SLOT YOURE OVERWRITING YOUR DEVICE MIGHT BRICK
Ok, thats over with
INFO:
This is just a simple script, in a simple ZIP, designed to clone all the devices ACTIVE slots in /dev/block/bootdevice/by-name to the INACTIVE ones
it does nothing more, nothing less.
For me, this solved some issues with lineage and custom roms on my device and keeps my mild ocd... well.. mild.
This will not touch any partition with the word logo in it (lowercase only for now, oops)
BASIC HOW-TO:
0) have basic knowledge of how android works, dont be stupid
1) flash rom
2) run AB-Cloner-test
3) If the test runs normal rename it to AB-Cloner.zip ( remove the word "test" from the zip name)
4) run AB-Cloner
5) ???
6) profit!
Tested devices:
Successful tests:
Motorola Z² Force
(report your success below)
Unsuccessful tests:
PLEASE report below, so no one else endangers their phones
Known Bugs/Issues:
currently the word test must be lowercase in the filename, if any letter is not lowercase in the word test IT WILL RUN THE ACTUAL COMMANDS. this will be fixed in RC2/Normal releases
You tell me ?
TODO:
add VOL key detection to cancel zip/ make choices
update detection: figure out which slot is newer, flash that one to older
aroma? probably not tho
You tell me?
C+ slots? if theres a device that needs it
Pictures:
{
"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"
}
Download:
RC1: here (GDrive)
Ae3NerdGod said:
I DO NOT TAKE RESPONSIBILITY FOR YOUR DEVICE BREAKING
THIS /WILL/ COPY YOUR BOOTLOADER FROM ONE SLOT TO ANOTHER
IF YOU DO THAT WITH A BOOTLOADER THAT IS OLDER THAN THE SLOT YOURE OVERWRITING YOUR DEVICE MIGHT BRICK
Ok, thats over with
This is just a simple script, in a simple ZIP, designed to clone all the devices ACTIVE slots in /dev/block/bootdevice/by-name to the INACTIVE ones
it does nothing more, nothing less
for me, this solved some issues with lineage and custom roms on my device
BASIC HOW-TO
0) have basic knowledge of how android works, dont be stupid
1) flash rom
2) run AB-Cloner-test
3) If the test runs normal Rname it to AB-Cloner ( remove the word test from the zip name)
4) run AB-Cloner
5) ???
6) profit!
Known Bugs/Issues:
- currently the word test must be lowercase in the filename, if any letter is not lowercase in the word test IT WILL RUN THE ACTUAL COMMANDS. this will be fixed in RC2/Normal releases
- You tell me ?
TODO:
- add VOL key detection to cancel zip/ make choices
- update detection: figure out which slot is newer, flash that one to older
- aroma? probably not tho
- You tell me?
- C+ slots? if theres a device that needs it
Download:
RC1: here (GDrive)
Click to expand...
Click to collapse
This is good work
([emoji3590]09-09-18[emoji3590])
PoochyX said:
This is good work
([emoji3590]09-09-18[emoji3590])
Click to expand...
Click to collapse
thank you!
FYI I just ran this on my G7 Power (Ocean) and it seemed to work just fine. I had a good Resurrection Remix install on Slot A (active) and some weird borked stuff on Slot B.
I loaded and ran the .zip via adb sideload, it copied everything over, and it all seems to work just fine now, and identical on both slots.
FYI when running it this way (adb sideload) the name included "-test" but there was no test. It just ran--luckily it seemed to work OK.
Oneplus 8 5G UW (IN2019) did not work