[Q] [htc A9191] can I change firmware ? - Android Software/Hacking General [Developers Only]

Hi, this is my first post on here.
Today my Chinese girlfriend bought me new htc's phone, I some times said I wanted to buy it. but all Android phones in mainland China (not Hongkong) are limited in network and android market. So I want to change this firmware to Hongkong's one or another countries'.
Can I do this ?
If yes, please let me know hot to do it.
Thank.

i have this problem oso.. htc-a9191 android 2.2 upgrade to 2.3; then my digi cannot support but maxis can support... how to solve???

try going to recovery if succeed then it's possible to change firmware.. there are two ways to do this:
1.Going Manually : Hold down the vol down key then press power... it will boot into recovery.. if not succeed do the second method:
2.download Android SDK or just the adb.exe executable then we are going to run it with command line so add the path to adb.exe like C:\Android_SDK\tools to your path variable then execute this in command line (cmd.exe):
1. adb devices (to see if your device is identified or no.. if your device is listed then go to step 2...)
2.adb reboot recovery (then your phone will boot into recovery.. if succeed you can change, if not then no)

Related

[ROOT][GUIDE] HBoot 2.02/2.10 SOFF - Goodbye Stranger - Upd. 02.25.11

I am sad to say the time has come to retire this post....Now before you get all panicky and ****, just sit your **** down, take your adderall and relax, damn antsy ass people. Anywho, with people our there like xHausx and others that have automated all of this there really isnt a need for me to keep this updated. I will keep the post here for archival purposes but, I will not be updating it, any further. I may pop into the thread here and there but probably not. I would like to thank all those that helped and supported me during this threads run. With out you we would still be stuck.
In the mean time if your looking to root your phone, check out xHausx's thread
here: http://forum.xda-developers.com/showthread.php?t=838448
And no I still dont recommend Clockwork or Unrevoked.
Till next time...Super Tramp - Goodbye Stranger
Archive of the guide as of 2/14/11
READ THIS GUIDE CAREFULLY SEE POST TWO FOR FAQ OR SEARCH THE THREAD.
Presenting the ONE AND ONLY surefire root method that backs up your RSA KEYS prior to rooting !!!!
Also I am aware that unrevoked has out their new tool. However while I was sitting in IRC, I saw many that it wasnt working for. So Until there is a surefire, easy method, I will keep this thread updated.
Credit goes to:
amoamare (Initial method)
toast (fake recovery and script)
unrevoked (thanks for your app)
amon_ra (fixed custom recovery)
chris1683 (thanks for the rom) (sprintlovers)
ryanza (z4root)
illogos, epicroot, xHausx, TrevE, Chubbzlou (Testing)
BooDaddy (RSA Backup Info)
and who ever else I missed
Help me finance my Vette!
zikronix
Disclaimer and well a little fun:
This has been tested on many phones and it worked fine...but if it breaks your **** dont come cry to me about it...you knew the risks! No one here is responsible if you break, brick, set fire, punch, smash, stab, destroy, your self, computer or your phone. The only person responsible is you! Just because it worked for me and others does not mean it will for you. Anytime you flash something its a risk.
Ladies and gentlemen... I've traveled over half our forum to be here tonight. I couldn't get away sooner because I had a POST coming in and I had to see about it. That phone is now rooted at and running well. I have two others comming in and this method has rooted many on the board. So, ladies and gentlemen... if I say my guide works you will agree. You have a great chance here, but bear in mind, you can lose it all if you're not careful.
Out of all methods that beg for a chance to root your phone, maybe one in twenty will work; the rest will be trolls-that's posters trying to get between you and the guide-to get some of the root action that ought by rights come to you. Even if you find one that has a simpler guide, and means to root, he'll maybe know nothing about helping. This is... the way that this works. This method is reliable like no other in this field and that's because its been tested and tested time and time again. I assure you, whatever the others promise to do, when it comes to the showdown, they won't be there...
Downloads
================================================== ====
STOP HERE READ THIS
This Method soley uses Amon_RA Recoveries....Period. A poor soul that lost his RSA keys (broken 4g forever) by recent clock work shenanaigans here
VX - Updated Amon Ra Recovery. Download Here: hboot_2.xx_soff-VX.zip
MD5: 27eb4a36ba01078193975fc93723dd60 <---VERIFY YOUR MD5, IF ITS NOT THIS REDOWNLOAD
Lets Get Rooted!
======================================================
Prerequsites:
Extract only the main zip file to a folder of your choice. I recommend the root of C:\ into a folder of your choice or on the desktop. Make sure you have the drivers installed for your phone (recommended: SDK Drivers or unrevoked hboot drivers) and USB debugging is on. This was setup for people running windows, if you have access to it do it on a 32bit version. I can't stress this enough you must use the adb.exe included with the package This is command line based do NOT double click the exe. Assume nothing, and cut and paste or type the commands EXACTLY as listed, they are case sensitive and each line is a seperate command. Oh and Read the FAQ and Warnings for f-sakes
1) Connect your phone to the computer (Rear USB Port Perferred) make sure the computer detects the phone (DO NOT MOUNT USB) If it doesnt install the drivers. Now master Reset your Phone (Menu>settings>Sd & Phone Storage>Factory Data Reset). Your phone will reboot. While your phone is rebooting it ctrl+alt+delete on your computer and open up task manager and click the processes tab look for anything that says adb.exe click it and hit end process.
2) Your phone should be booted and in the rom. You can skip the setup. On your phone enable install applications from unknown sources.(menu>settings>applications>unknown sources) and turn on usb debugging.
3) Open a command prompt (do NOT click adb.exe) and change to where ever you extracted the files to.
4)Type the following (this must be excuted from the folder you extracted to)
adb push root/unrevoked-forever.zip /sdcard/
adb push root/mtd-eng.img /sdcard/
adb push pc36img/PC36IMG-ENG.zip /sdcard/PC36IMG.zip
adb push pc36img/PC36IMG-MR.zip /sdcard/PC36IMG-MR.zip
adb push root/flash_image /data/local/
Click to expand...
Click to collapse
5) Now were gonna install z4root. When its done look at your phone z4root should be running. Select temporary root... It will go thru the process will eventually come to a white screen *Wait* after a sec or so screen will come up saying temp root was a success. Ok so now type the following
adb -d install -r root/z4root.apk
adb shell am start -a android.intent.action.MAIN -n com.z4mod.z4root/com.z4mod.z4root.z4root
Click to expand...
Click to collapse
6) Your command should still be open and you should be in the directory where you extracted the files. Once you have typed "su" command below look at your phone and click allow for SuperUser...Ok so now type the following from the command prompt
adb shell
su
Click to expand...
Click to collapse
6A) REQUIRED RSA BACKUP This will back up your RSA keys just in case something goes wrong in that department. You should still be in your command window inside the shell with a #. (The following came from this thread)
mkdir -p /sdcard/nandroid/RSA-PR-BACKUP
cat /dev/mtd/mtd0 > /sdcard/nandroid/RSA-PR-BACKUP/wimax.img
This saves it in a file that can actually be restored. This next step is another type of backup just for good measure
busybox sed -n '/BEGIN CERTIFICATE/,$p' /dev/mtd/mtd0 > /sdcard/rsa_OEM.key
This will dump the RSA keys to a text file on your SD Card named rsa_OEM.key
Mine was about 4575 KB in size, but the size could vary. Go ahead and switch the phone's USB connection over to "Disk Drive" and then browse to your SD Card and verify that the file rsa_OEM.key is indeed on the card.
Proceed to Step 7
Click to expand...
Click to collapse
7) You Should still be at a "#". This means you have root if you see a "$" or some other error message. Reboot your phone, check your drivers, usb debugging and cable and start over. If you got a "#" You can Proceed. You should still be in the shell at a "#" If not start over...Otherwise
chmod 0755 /data/local/flash_image
./data/local/flash_image misc /sdcard/mtd-eng.img
sync
Click to expand...
Click to collapse
8) Now we are going to reboot your phone into the boot loader to flash the first PC36IMG.zip. You should still be in the shell So Type:
reboot bootloader
Click to expand...
Click to collapse
9) Once your phone is in the boot loader highlight bootloader, and press the power button. It will load the PC36IMG File...When it ask you to flash press VOL-UP. You will notice that it says bootloader bypassed and maybe some other errors. Dont worry this is normal. Once the flash of the file is done it will ask to reboot, Select NO by Pressing VOL-DOWN. Now some people have gotten some errors here and there during the flashing just continue as normal.
10) You should still be in the boot loader at this point. Scroll down to recovery and press the power button. It Should take you to a red triangle. If not and you get stuck at a white htc screen pull the battery and then repower the phone with power + vol down and select recovery. When you see the red triangle. Type the following (IF YOU GET STUCK HERE CHECK THE FAQ):
adb push recovery /
adb shell busybox --install /sbin
adb shell nohup /sbin/recovery &
Click to expand...
Click to collapse
With any luck you should be at a recovery (green screen with text)
11) Select enable USB-MS. This will mount your sdcard. Look in the root of your sdcard and you should have two files. One named PC36IMG.zip and one named PC36IMG-MR.zip. Rename the file named PC36IMG.zip to PC36IMG-ENG.zip and then rename PC36IMG-MR.zip to PC36IMG.zip when your done follow the instructions on your phone to disable usb (press power) then proceed to step 12
12) Now Select flash zip from the menu and choose unrevoked-forever.zip. Wait for it to complete. Select Reboot from the menu.
Now pay attention. It might kick you back into:
BOOT LOADER: See 12A
ROM: See 12B
WHITE HTC SCREEN: See 12C
12A) Ok so you got kicked to the boot loader. It should scan your card and find the PC36IMG.zip chose yes to flash this file and when it ask you to reboot....reboot by pressing vol-up....Proceed to step 13
12B) Ok so the phone booted into a rom. Power the phone off. Then repower the phone on pressing power and vol-down at the same time. It should take you into the bootloader and scan your card and find the PC36IMG.zip chose yes to flash this file and when it ask you to reboot....reboot by pressing vol-up....Proceed to step 13
12C) Ok so the phone is stuck at a white htc screen. Power the phone off by pulling the battery. Then repower the phone on pressing power and vol-down at the same time. It should take you into the bootloader and scan your card and find the PC36IMG.zip chose yes to flash this file and when it ask you to reboot....reboot by pressing vol-up....Proceed to step 13
13) Ok your phone is rooted now, and you should be inside the rom. The rom you just flashed is Sprint Lovers rom with the modified recovery. Download a rom of your choice copy it to the root of your sd card and flash it. But type the following first
adb shell mv /sdcard/PC36IMG.zip /sdcard/PC36IMG-MR.zip
adb reboot recovery
Click to expand...
Click to collapse
14) You Should be in the recovery menu now (green text screen). Do a backup by navigating to backup/restore press power to select then do a Nand backup in the next menu. Once thats done, select return, then reboot or flash a rom of your choice. If you flashed a different custom rom than the one thats included in the package cool. If not no big deal eitherway. Do a PRL/Profile update while in the rom after the phone is done rebooting. Your Done.
15) Read the FAQ for questions
==========================================
FIX BROKEN RECOVERY
This is really only needed if you rooted with one of the previos guides version 6 or lower or if you installed a different recovery like I told you not to. It installs amon_ra 2.2.1
1) Download File PC36IMG_Recovery.zip and Rename to PC36IMG.zip.
copy to the root of your SDCard and power off phone
2) Power your phone back on into the boot loader by holding power and vol-down until your presented with a white screen. It will read the pc36img.zip and as you if you want to flash. Say yes. Then it will ask if you want to reboot, VOL+UP for yes.
3) If your rom gets tossed in the process. Reboot your phone into bootloader select recovery, and reflash your rom....DONE
================================================
UNROOT GUIDE
NOTE: This will erase all data on the phone. (Will not erase data on the SDCard)
1) If your on Hboot 2.10 Download the PC36IMG.zip Here. If your on Hboot 2.02 Download the PC36IMG.zip here then Unrevoked s-on here rename the pc36img file to pc36img.zip copy that and the unrevoked s-on tool to the root of your sd
2) Power your off. Power the Phone back on into the boot loader by holding power and vol-down until your presented with a white screen.
3) It will scan for the pc36img.zip. Select no to flash. Select recovery from the menu. Once in recovery choose flash zip from the menu, and select unrevoked forever s-on.
4) When its done flashing select reboot from the menu.
5) From here either run the official ruu or boot back into the boot loader (see step 2). When it scans and ask you to flash the pc36img.zip select yes then yes to reboot.
Click to expand...
Click to collapse
FAQ
FAQ:
Your here cause something went wrong right? Ok thats fine. This list isnt extensive but its here to provide quick answers to some weird or common questions. New questions and problems are added to the bottom.
Q: Will this downgrade my hboot
A: No. I used to have an hboot downgrade but it was bricking peoples phones. However is you want to risk bricking your device, visit this thread here. I I advise against this. This bricked alot of phones which is why I pulled it.
Q: How do I install the Hboot Drivers
A: Check this here
Q: I get "error: more than one device and emulator"
A: kill the adb.exe tasks in task manager or reboot your computer
Q: Step #9 my phone does read the PC36IMg.zip
A: If you renamed the zip file make sure it doesn't say PC36IMG.zip in the name remember that xp and up on windows doesn't show the file ext by default so if you see PC36IMG.zip chances are its named PC36IMG.zip.zip
Q: Why cant I use Clockwork Recovery
A: At the moment its not coded for the new partitions. Just read the first few pages of this thread or check this here
Q: What Hardware does this work for
A: All currently known hardware 0001-0004
Q: What Hboot's does this work for
A: It was built for 2.02 and 2.10 however it will work for all version its just there are easier ways for those
Q: I think I messed up can I just start over.
A: Yes. Its recommended if you want to start over run the official ruu.
Q: This is very complicated
A: It is...thats why there is instructions
Q: Will this erase my data
A: Yes but not from the SDCARD
Q: Can I deleted the files off my SDCARD when done
A: Yes, except for RSA_OEM.KEY and WIMAX.IMG
Q: I get permission denied or device offline when trying to step 10
A: Check here or here or here this might work for you
Q: I used clockwork it seems to work fine.
A: It might but considering the partition information is not correct. You may have just over wrote your wimax keys and broke 4G. Have fun with that like this poor guy here
Q: This uses unrevoked in one of its steps? Explain?
A: There have been some concerns that this uses unrevoked-forever in one of its steps. As far as we know that Unrevoked 3 (not to be conufused with unrevoked-forever) is causing some radio issues with hardware in general and new hardware. Unrevoked-forever does not appear to bork the radio like unrevoked 3 does. This is apparent by the many success stories. However Unrevoked3 could very well possibly destroy your radio/wimax/brick if used.
Q: I get device not found
A: Install the drivers for your phone, (Unrevoked, ADB)
Q: Camera doesnt work after doing this
A: Flash a new rom thats current. Like SteelRom, Fresh, Stock Rooted. The issue here is the Hardware is different. NO CUSTOM KERNELS
A2: Reports say they changed the camera provider/hardware. And the drivers are different! Using a rom based off the latest release and kernel should fix it As Discussed here and here and here
Q: When I go to recovery. I get a red triangle.
A: See Step 10
Q: This doesnt work!
A: Yes it does if you follow the directions, Unless some other bull**** decided to popup!
Q: CM6.x doesnt work
A: See Question 7....Nothing I can do about that if the kernel doesnt support your camera/device.
Q: My phone boot loops now...You broke my ****!
A: I didnt break your ****. You broke your own ****! Its not broken so chill out (well it might be but probably not). What rom did you flash? Did you flash a custom kernel? Did your rom come with a custom kernel? I bet your using a custom kernel. Try a rom like Steel Rom, Sprint Lovers
Q: How do I back up my RSA Keys
A: Check here for the latest up to date information. Or run this command from the shell
cat /dev/mtd/mtd0 > /sdcard/wimax.img
Click to expand...
Click to collapse
Q: My 4g Doesnt work
A: Was it broken prior to the s-off, what steps did you take. Are you running AOSP ROM or Another kernel?, Did you try a different rom? What version is your phone? Do you have SwitchPro Widget installed? (uninstall it), Did you try to run unrevoked3 prior to this? After flashing the radios and stock kernel based rom did you do a data and prl update? Does the mac behind your battery match whats in about phone (4g has to be on to see mac) Also try the tree.xml fix posted
adb shell
ls /data/misc/wimax/
look for a file with your macaddress ending in .tree.xml. you want to move that to another location so it gets regenerated. (the following command basically renames it.)
mv /data/misc/wimax/(Your-mac-address).tree.xml /data/misc/wimax/(Your-mac-address).tree.xml.old
4. Start 4G may not connect
5. Do a prl/profile update
6. Power off the phone and power it back on. Try it
7. PRL/Profile. Try it
Click to expand...
Click to collapse
Q: 4G is still broke.
A: Check your RSA keys
adb shell
cat /dev/mtd/mtd0 | grep RSA
returned output show appear as this:
# cat /dev/mtd/mtd0 | busybox grep RSA
cat mtd0 | busybox grep RSA
RSA-REQUEST
RSA-REPLY
RSA-REJECT
RSA-ACK
RSA-1024
RSA-REQUEST
RSA-REPLY
RSA-REJECT
RSA-ACK
RSA-1024
RSA
ReRSA
RSA requests
RSA replies
-----BEGIN RSA PRIVATE KEY-----
-----END RSA PRIVATE KEY-----
#
It should look just like the above
the important lines are BEGIN RSA PRIVATE KEY and END RSA PRIVATE KEY.
If you have those two lines, your keys are still likely to be intact.
If those two lines are missing, your keys are likely missing.
/dev/mtd/mtd0 is where the wimax image is stored.
Click to expand...
Click to collapse
Q: OK I think My Keys are tossed. We made a backup right? So how do I restore it?
A: This post or post should do it for you
Q: My Phone says its not rooted.
A: If you have s-off your rooted. Simple as that. Try a different rom if you want. The second pc36img.zip file you flashed is Sprint Lovers and is a very nice rooted rom.
Q: When I try to get into Fastboot by pressing VOLUME UP and booting the phone, my phone instead buzzes three times and acts dead. What happened?
A: The S-OFF update also enables Qualcomm Diagnostics mode on your phone, which is entered by doing what you just did. You can exit this mode (and boot normally) by removing the battery and USB cable.
Q: Can you tell me what this does?
A: Read the guide? Basically your downgrading the phone, so you can flash unrevoked because htc "comically fixed" the phone. Then your re upgrading the phone back to shipping radios, system, pri, nv, kernel...all the while with keeping s-off
Q: How did you get to be so cool
A: If you have it, you don’t need it. If you need it, you don’t have it. If you have it, you need more of it. If you have more of it, you don’t need less of it. You need it to get it. And you certainly need it to get more of it. But if you already don’t have any of it to begin with, you can’t get any of it to get started. Which means you really have no idea how to get it in the first place, do you? You can share it, sure. You can even stockpile it if you like. But you can’t fake it. Wanting it, needing it, wishing for it. The point is, if you’ve never had any of it, ever, people just seem to know.
Q: Do you really own a vette?
A: Yes, and a backpack with jets!
Q: Whats with you and the dots ...
A: ...
Q: Your Kind of an Cocky Asshole
A: Yea...I Get that. Oh well. I cant fix stupid or ignorant.
What is the point of getting the new HBoot?
sorry, wrong question
abiezer said:
What is the point of getting the new HBoot?
Click to expand...
Click to collapse
there is no point in getting a new hboot....this tool is for those that have phones with the new hboot....that unrevoked wont work on.
this is not the new hboot
Oh I see so this is basically for people who couldn't root to be able to root. Got it. Thanks.
Dumb question, sorry trying to keep up with this while at work. Once I do this, then I still need to run Unrevoked, correct?
shepkc said:
Dumb question, sorry trying to keep up with this while at work. Once I do this, then I still need to run Unrevoked, correct?
Click to expand...
Click to collapse
its included in the script it tells you how to do it.
update failed, said main version is older...
its working for some but not others...i dont know why the main version is older thing...
i think we have ironed out the mainversion deal...
looking into it now.
Should be fixed now...so try it I guess.
v2
Looks like your V2 is working, I didn't run into the main version failure. Flashing as I type, I hope slyder got this to work.
Confirmed, V2 works
alright brotha your v2 of the batch file works like a charm. S-OFF confirmed on HBOOT 2.02. Thanks to everyone involved in making this happen.
Outstanding
Sent from my PC36100 using XDA App
On a brand new fresh 2.2 out of the box running HBOOT 2.02 I got "Main version is older". Are there any prerequisites i have to run to get this to work? I just reinstalled 2.2 and ran the script and got main version is older.
did you download version 2
do you have gtalk
I did download v2, and I do have gtalk.
b0r0b said:
I did download v2, and I do have gtalk.
Click to expand...
Click to collapse
you got PM....i want to know exactly whats happening.
Main version is older
I have also tried with V2 and get the "Main version is older".
Baseband
2.15.00.09.01
Software
3.30.651.2
PRL
60671

[Q] ZOPO ZP990 wont boot after changes to /system/build.prop

Hello, I am new to xda-developers and have just joined up.
I have gone to great lengths to find an answer to my problem with Google and have searched this forum.
Not having any luck I have decided to call out for help.
My situation
- Country: Australia
- Model: ZOPO ZP990 Android phone.
- Android 4.2, Jelly Bean
- Phone is "rooted".
- No recovery backup was ever made.
- My 3G wasn't working. The best I could achieve was "2G EDGE" data connections.
- I have a good HSDPA connectivity with my old LG Android P500 phone in my area.
- As I bought the Zopo phone in China I don't have the option of "after sales service".
- I am an Android newbie and I know very little about Android systems in general.
I was very happy with this phone, except that I was having issues connecting to 3G.
I had used Mobileuncle to configure for the specific 900/2100MHz 3G service in Australia.
Setting the 3G bands with Mobileuncle for my region did not correct my problem with no 3G access.
I then followed the advice to make changes to /system/build.prop
As there were no similar entries in my default build.prop I added the following lines to the very end.
# Start Support for Australian 3G
ro.ril.hsxpa=2
ro.ril.hsdpa.category=5
ro.ril.enable.3g.prefix=1
ro.ril.hsupa.category=5
ro.ril.enable.dtm=1
ro.ril.gprsclass=12
ro.ril.enable.a53=1
# End Support for Australian 3G
I made a copy of the original /system/build.prop to /system/build.prop.bak as a backup.
I made the changes using Notepad++ (on PC) and an Android File Manager (provided root access) app.
I then rebooted and my phone hangs after it presents a ZOPO musical/visual start-up advert presentation.
My phone wont boot !!!
--------------------------------------------
<by pressing buttons on power-up I get the following>
Android system recovery <3e>
Enter: OK Key, Select : Vol UP/ Vol down
Reboot system now
apply update from ADB
apply update from sdcard
wipe data/ factory reset
wipe cache partition
--------------------------------------------
Using ADB(Android Debugging Bridge) Version 1.0.31
(I am using Mini-SDK and not the full Android SDK)
I have "Java Runtime Engine" but not "Java SDK" installed.
I connect the phone to my PC via USB and enter the "Android system recovery <3e>" environment.
I select the "apply update from ADB" on my phone.
I then enter the following commands into my PC.
C:\mini-sdk>adb version
Android Debug Bridge version 1.0.31
C:\mini-sdk>adb devices
List of devices attached
0123456789ABCDEF sideload
C:\mini-sdk>adb usb
error: closed
C:\mini-sdk>adb shell
error: closed
Besides the above commands I cannot get ADB to do anything useful.
I have "USB Debugging" turned off at the phone so I suspect this is why ADB doesn't work.
I know very little about ADB only what I have recently learnt with Google.
--------------------------------------------
I then downloaded the latest ZP990 ROM and Flash Tool V4.2
While I found the instructions straightforward I cannot establish communication between PC and phone via USB.
(I have the correct Android drivers installed on my PC and had full USB functionality before this problem started.)
Once again I suspect the fact that my "USB Debugging" is turned off prevents Flash Tool to work.
--------------------------------------------
I've noticed there is an "apply update from sdcard" in the "Android system recovery <3e>" environment.
I wonder if I can exploit this?
Is there a recovery ROM on the internet that I could download from the net to use on my sdcard?
If I could get any ROM to load, I could later use Flash Tool to do the final ROM upgrade.
Does anyone know if I could use the "apply update from sdcard" from "Android system recovery <3e>" to install a new ROM.
--------------------------------------------
Can someone please help me?
I work in the electronics/IT field, but I know very little about Android systems.
So all I need is guidance on moving forward.
If I sound like I know more about Android that is because I have done a lot of research on the internet to try and fix my phone.
--------------------------------------------
Are you able to do an ADB PULL of the backup you took, rename it on your PC to build.prop, do an ADB REMOUNT then ADB PUSH it back?
I fixed it myself !!!
No need to help me.
I found what I was looking for on the various Android websites around.
I needed to first instal the Mediatek USB VCOM drivers.
Install the latest copy of SP Flash Tool on my PC.
Down load the latest ZP990 ROM from the ZOPO website and unpack it.
Remove battery from phone for a short period. Put the battery back, but don't power up.
Start SP Flash Tool
Select the scatter-loading file from the ROM I unpacked.
Press F9 (or hit Download button) and connect your phone into the computer via USB data cable.
Things went much easier than I expected.
Lost my data, but I got my phone back. :good:

[Help] Blu Vivo 4.8

Hello friends, I need your help...
Since i did a Dalvik-Cache clean on my phone, it got stuck on the bootlogo...
I can't find anywhere the stock rom and the scatter file to try amend this with SPTool since I dont have CWM or TWRP.
If there is a way to just get my files, pictures and music back will be enough help...
:crying:
Since no one bothered to help me, I managed to find a solution.
Will share here what i done.
1- Downloaded adb and put at C:/adb
2- Downloaded my phone usb/adb drivers.
3- Put my phone into factory mode by holding Volume-down key and power
4- By doing previous step and connecting the usb cable on the phone to pc, is possible to use adb commands
5- Used the command = adb pull /storage/sdcard0 C:/adb/Phone-Files (Can't start "adb shell" otherwise file/folder copy is blocked) from the cmd at the adb folder
6- Waited a hour and half to get everything from my phone to the folder = C:/adb/Phone-Files
I'm on my way to learn how to fix the Dalvik-Cache deletion.
Maybe getting the stock rom somewhere and using pull may solve... :fingers-crossed:

[Guide] Newbie to Photon Q 4G LTE Rooting w/ Ice Cream Sandwich

Purpose: The purpose of this guide is to help collect all information and steps needed to root a Motorola Photon Q 4G LTE and use Clockwork Mod. When I looked for tutorials there were no updated ones that detailed how to do this with the latest android update (as of May 2014) for the Photon. Some steps may have been / were copied from various posts & guides around the internet, again this is just a collection of information.
Goal: A user who just opened his Photon Q 4G LTE and did all the factory updates should be able to get his phone rooted by the end of the guide.
Note: I started this guide but sadly the ribbon cable on my Photon Q 4G LTE broke and I just decided to switch carriers. I never got back to proof reading this guide while it was still fresh in my memory but if anyone sees and issues just let me know.
Unlock the Bootloader:
I unlocked the bootloader because I wanted to install ClockWork Mod and read that you had to. Not sure if you need to do this just for root access. I wanted CWM so that I could create a backup of this phone as is came from the factory so if I want to restore down the road I can. Unlike my Samsung it seems difficult to find the factory software for the Photon Q so this seemed like the best way to get it. Also nice to have the ability to take backups of my phone every so often. Assuming your phone is new I recommend that you also take a factory backup once clockwork mod is on before installing any other apps.
1. Download and install the drivers for the Photon Q from Motorola here ( https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481 )
2. Download this ZIP package which contains the tools you need for most of the steps here ( https://od.lk/f/MjRfMjc2MDc1Ml8 )
3. Head over to Motorola’s bootloader unlock site and sign in / register ( https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b )
4. Put your device in fastboot mode by powering off, waiting a moment, then pressing the “power” and “volume down” buttons simultaneously and releasing the “power” button ONLY after a few seconds. Once you see the fastboot screen you can release “volume down” as well.
5. Unzip and open the folder with the ZIP files from Step 2 and open a command prompt or terminal (in Windows 7 hold “Shift” and right-click in the folder and select “open command window here”.
6. In the prompt, type “fastboot oem get_unlock_data” without the quotes.
7. You will see 5 or so lines with either “(bootloader)” or “INFO” in front of them. Use notepad or some other basic text editor to paste together the 5 lines of output into one continuous string WITHOUT (bootloader) or ‘INFO’ or white spaces in front of them so your string looks something like this: 0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2AC0C39F951A3E5#1F532800020000000000000000000000
8. Check if your device can be unlocked by pasting the string in the field on Motorola’s page on their section 6. and click “Can my device be unlocked?” If you have a problem with this most likely the string you pasted in the box has spaces or extra / incorrect characters. Try again.
9. Open the email and get the unlock code. My email ended up in the “Promotion” category inbox instead of my normal inbox so if you don’t see it check in other places such as “Spam”.
10. Put your device in fastboot mode again by powering off, waiting a moment, then pressing the “power” and “volume down” buttons simultaneously and releasing the “power” button ONLY after a few seconds. Once you see the fastboot screen you can release “volume down” as well.
11. Connect the device to the computer with a USB cable. You'll get a confirmation message on the device to indicate that it's connected.
12. Open the folder with the ZIP files from Step 2 again and open a command prompt or terminal (in Windows 7 hold “Shift” and right-click in the folder and select “open command window here”.
13. In the prompt, type “fastboot devices” without the quotes and make sure your device shows up.
14. To unlock the bootloader, enter the following in the prompt “fastboot oem unlock UNIQUE_KEY” without quotes where you replace the “UNIQUE_KEY” with the code you received in the email. It is case-sensitive.
15. If the line was entered correctly, you will see a message confirming that your device was unlocked.​Install Clockwork Mod:
1. Download the latest ClockWorkMod recovery for the Photon Q from clockworkmod.com/rommanager and place the file in the same folder as the files from Bootloader Step 2. Be careful to select the right image!
2. Connect the Photon Q to the computer via USB.
3. Open the folder with the ZIP files from Bootloader Step 2 again and open a command prompt or terminal (in Windows 7 hold “Shift” and right-click in the folder and select “open command window here”.
4. Put your device in fastboot mode again by powering off, waiting a moment, then pressing the “power” and “volume down” buttons simultaneously and releasing the “power” button ONLY after a few seconds. Once you see the fastboot screen you can release “volume down” as well.
5. In the prompt, type “fastboot devices” without the quotes and make sure your device shows
a. If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine. See fastboot documentation for more info.
b. If you see "no permissions fastboot", make sure your UDEV rules are setup correctly.
6. Flash ClockWork Mod recovery onto your device by entering the following command in the prompt “fastboot flash recovery image.img” without the quotes where “image.img” is the full name of the file you downloaded in Step 1.
7. Once the flash completes successfully, reboot the device into recovery to verify the installation by powering off the phone and then holding both “Volume Up” & “Power” simultaneously until you see ClockWork Mod on the screen. From here you can take a backup (recommended) if you want to like I did.
o Note: Some ROMs overwrite recovery at boot time so if you do not plan to immediately boot into recovery to install CyanogenMod, please be aware that this may overwrite your custom recovery with the stock one. ​Root the device:
1. Boot the Photon Q normally and go to Settings>Developer Options> and enable USB Debugging. You may have to turn on Developer Options as well if they are grayed out.
2. Connect the Photon Q to the computer via USB.
3. Navigate to the folder with the ZIP files from Bootloader Step 2 again open the run.bat file.
4. Press Enter after reading the disclaimer (if you want) and wait for the file to finish running.
5. After it is done you can press enter again to close the prompt and disconnect your phone
6. After the phone reboots automatically you will see a new Super User app in your app list. You are now rooted.​
FYI installing TWRP will offer to automatically root the device for you when you reboot back into Android.
Also, CWM for our devices is horribly outdated, and last I checked completely unable to flash any KK-based ROM. I wouldn't recommend it - OpenRecovery or TWRP are my recommendations.
arrrghhh said:
FYI installing TWRP will offer to automatically root the device for you when you reboot back into Android.
Also, CWM for our devices is horribly outdated, and last I checked completely unable to flash any KK-based ROM. I wouldn't recommend it - OpenRecovery or TWRP are my recommendations.
Click to expand...
Click to collapse
The two months I had my Photon Q working CWM worked great for me. Did a few backups and didn't have to re-root after each boot. But it always helps to have more options so thanks for mentioning both alternatives!
protivakid said:
The two months I had my Photon Q working CWM worked great for me. Did a few backups and didn't have to re-root after each boot. But it always helps to have more options so thanks for mentioning both alternatives!
Click to expand...
Click to collapse
I'm pretty sure CWM won't flash KK-based ROM's as I stated previously.
Also, you shouldn't have to re-root - TWRP just does the rooting for your if you are installing a custom recovery for the first time so you don't have to do it manually .
arrrghhh said:
I'm pretty sure CWM won't flash KK-based ROM's as I stated previously.
Also, you shouldn't have to re-root - TWRP just does the rooting for your if you are installing a custom recovery for the first time so you don't have to do it manually .
Click to expand...
Click to collapse
Thanks again! I just used the stock rom but rooted during my brief time with the phone but this will help those who wish to use KK on the Photon.
RISING THIS TREAD FROM THE DEAD!!!
WHO STILL HAS THIS PHONE WORKING??
i blue screened my LG G3 so i pulled this phone off my dash in the bimmer to possibly try to root but it runs so damn slow now. any support will be much appreciated this is by far the most reliable device i ever purchased (400 bucks out the door brand new fml)
i will try to root later this week but big shout out to XDA for all thier threads on android ive been rooting since the
optimus line
cheers!

"This phone model does not support deep testing." Is it possible to bypass that screen in the Realme's deep testing app?

Update: after a break for a couple of days, this appears to work again. But probably not for long -- so better try it if and while it's still up ;-)
I was able to do just that (and unlock the bootloader on my phone) some two months ago (in February 2023).
I did by using this perl script of mine to simulate the https requests performed by the deep testing app.
My phone was a Realme 9 5G (RMX3474), the EU/GDPR variant.
A dry run with bogus serial num and imei strongly suggests that they haven't "fixed" it yet and it may still work.
I also suspect that it may work with other Realme phones not supported by the deep testing app.
But I don't have any spare phone (and I will not test my luck by locking it back ;-)), so I'll be grateful if anyone with a locked Realme phone would give it a try (the deep testing app would still ask you for confirmation, you don't have to unlock your phone if you don't want to).
turistu said:
I was able to do just that (and unlock the bootloader on my phone) some two months ago (in February 2023).
I did by using this perl script of mine to simulate the https requests performed by the deep testing app.
My phone was a Realme 9 5G (RMX3474), the EU/GDPR variant.
A dry run with bogus serial num and imei strongly suggests that they haven't "fixed" it yet and it may still work.
I also suspect that it may work with other Realme phones not supported by the deep testing app.
But I don't have any spare phone (and I will not test by luck by locking it back ;-)), so I'll be grateful if anyone with a locked Realme phone would give it a try (the deep testing app would still ask you for confirmation, you don't have to unlock your phone if you don't want to).
Click to expand...
Click to collapse
Thank You!
It realy works!
Thanks,
Worked for me with Android 13/RealMe UI 4.0.
Now to magisk...
After unlocking the phone, I'm looking for the boot.img.
I can find firmware update package for UI3.0, but none seems available for 4.0.
Could someone point me to it ? (either boot.img or ofp package)
Is there a way to use this script on realme 9 pro 5g eu rmx3472?
Edit: It works perfectly and i was also able to change my region to ru.
mister_slowhand said:
After unlocking the phone, I'm looking for the boot.img.
I can find firmware update package for UI3.0, but none seems available for 4.0.
Could someone point me to it ? (either boot.img or ofp package)
Click to expand...
Click to collapse
Try https://rms01.realme.net/sw/RMX3472GDPR_NN.X.NN_YYYYMMDDHHMM0000.zip,
(replacing the N, Y, etc with the actual version of the firmware).
Also the variants with .7z instead of .zip.
hatbo said:
Thank You!
It realy works!
Click to expand...
Click to collapse
Hey lads,
Could you post me here some steps how to install and unlock bootloader using that script PERL ?
I'd really appreciate it. Cheers.
Thanks. Rob
RobertoSt25 said:
Hey lads,
Could you post me here some steps how to install and unlock bootloader using that script PERL ?
I'd really appreciate it. Cheers.
Thanks. Rob
Click to expand...
Click to collapse
As already mentioned at the end of that github page, you can use the "Strawberry Perl" distro to run that perl script on Windows.
1) First install strawberry perl
2) download the deeptesting-junk.pl script
3) start the "perl command prompt" (it should be the first result when you type "perl" in window's search box)
4) inside the command prompt change to the directory where you had downloaded the script
5) run the commands and follow the instructions from the github page. Take care to replace the dummy HHH and DDD with your actual serial number and IMEI ;-).
If you have problems with those instructions (e.g. the deeptesting app still does not work, despite the script getting a successful result to the "ckeckApproveResult" command), please mention exactly what happened.
I love you Turistu, thank you for the guide!
I've had the problem, that the device wasn't getting recognized in fastboot mode.
That is because the OnePlus Fastboot USB Drivers are NOT SIGNED!
You have to restart Windows with advanced startup settings, and deactivate driver signing. So that Windows trusts unsigned drivers.
Then you can restart Windows in that mode, settings -> windows update -> advanced options -> reset options -> advanced restart. Go to advanced boot -> deactivate usb driver signing (option 7), start the pc with that option.
AND THEN you can boot your device into fastboot mode, go into your drivers and if it's still coming up as unrecognized, right click it and update it's drivers manually with the oneplus drivers.
Then it should work for you, too. Gave me lots of Headaches.
I have attached the Oneplus drivers i've used for fastboot and a patched boot.img with magisk 26.1 from RMX3311_11.C.10_EU_202303171905.
You did a great job! Thank you!
PS. Dacă ești român, ești foarte tare frate!
turistu said:
As already mentioned at the end of that github page, you can use the "Strawberry Perl" distro to run that perl script on Windows.
1) First install strawberry perl
2) download the deeptesting-junk.pl script
3) start the "perl command prompt" (it should be the first result when you type "perl" in window's search box)
4) inside the command prompt change to the directory where you had downloaded the script
5) run the commands and follow the instructions from the github page. Take care to replace the dummy HHH and DDD with your actual serial number and IMEI ;-).
If you have problems with those instructions (e.g. the deeptesting app still does not work, despite the script getting a successful result to the "ckeckApproveResult" command), please mention exactly what happened.
Click to expand...
Click to collapse
Hello there,
I tried your method, I did everything step by step and it actually worked and it did unlock the bootloader.
However after yelow sign saying the "device is unlocked" went black screen, rebooted and again fastboot mode.
Now I really do not know what to do -.-
Any advice would help.
Thanks Rob
RobertoSt25 said:
However after yelow sign saying the "device is unlocked" went black screen, rebooted and again fastboot mode.
Click to expand...
Click to collapse
If the top of the screen has "START" in green letters, then just press the power button.
BTW, what phone model do you have?
turistu said:
If the top of the screen has "START" in green letters, then just press the power button.
BTW, what phone model do you have?
Click to expand...
Click to collapse
yes top of the screeen is START green, but when I pressed power just keeps rebooting into fastboot.
RMX 3474 REALME 9 5G
Thanks

Categories

Resources