Getting "Your Device isn't supported by Mi Unlock" error while unlocking bootloader - Xiaomi Redmi Note 3 Questions & Answers

Getting "Your Device isn't supported by Mi Unlock" error while unlocking bootloader
i have unlocked my bootloader officialy and installed cm14.1 rom by abhishek this rom replaced my device's bootloader with cyanogenmod bootloader so afterthat i flashed stock miui 8.0.5 through mi flash tool but now when i try to unlock my bootloader it is giving error "your device isn't supported by mi unlock" also when i checked for unlock permission on official website it is showing "your request has been rejected"
so plz someone explain me what is the actual problem and whats the solution for this
Thank You

maybe you have a vendors rom, use the edl and flashboot method and install a fresh rom and try again
https://www.reddit.com/r/Xiaomi/wiki/miui/flashofficial

fardeenah said:
maybe you have a vendors rom, use the edl and flashboot method and install a fresh rom and try again
@fardeenah i have flashed latest stable rom Miui 8.0.5 by miflash tool but still i am getting mentioned error hope it will have any solution
Click to expand...
Click to collapse

well your request for bootloader unlock has been rejected, can u apply for it again? simply say you want to install rom and that you are a developer, also make sure you are running the developer version of the rom when u try to unlock

Flash fastboot global developer rom through miflash (EDL Mode) it will solve the issue

@fardeenah there is no option to reapply now what should i do

@xelerater01 already flashed global beta rom 6.11.24 by edl still same error is coming

post in this forum
http://en.miui.com/type-64-717.html
if everything fails, create a new account and reapply
and follow this guide
http://en.miui.com/thread-199580-1-1.html
and
http://en.miui.com/thread-200858-1-1.html
good luck.
clear your browser before reapplying or use another browser

Install china fastboot dev rom through edl interface and than use MI Unlock Tool. It will work.

Try unlocking the unofficial way.

I have tha same problem
Inviato dal mio Redmi Note 3 utilizzando Tapatalk

Same problem here too. Any solution?

[quote name="abihary" post=69600823]check your bootloader, it seem you relock your bootloader. if yes, you can unlock it using miunlock & reboot into rom.[/QUOTE]<br />
<br />
Wait don't worry I will be uploading the correct files and procedure for doing that.<br />
<br />
The thing is your phone is bricked and nothing to do now right.?<br />
Theres a solution wait... Uploading that<font color="Silver"><br />
<br />
---------- Post added at 10:54 AM ---------- Previous post was at 10:40 AM ----------<br />
<br />
</font>[quote name="innynizty" post=69429358]Hello all ! Sry for my english but i think you can understand me <br />
<br />
<br />
<br />
The problem is with my phone. :crying:!<br />
I wanted to get the MIUI rom but when i install in twrp and reebot phone they stands in the place . I can only see logo all the time, nothings happen ;/ <br />
. I cant enter the recovery, only i cna see flashing logo and phone switches off. What can I do ? <br />
All I know is I can enable fastboot mode :c <br />
<br />
<br />
Help me please :C [/QUOTE]<br />
<br />
The solution is here:<br />
download the required files from the given link: [50mb]<br />
<br />
https://mega.nz/#!1NhDTQoR!cP7vrchwswOfj3oHQ5saZ2d0JkcmunEn5pqyOcpZDoE<br />
<br />
INSTRUCTIONS: [redmi note 3]<br />
1. Get into fastboot mode. Charge the phone first. Hold the power button and the volume down button simultaenously.<br />
2. If you can open your current rom, open developer options by clicking on the build no several times in the about phone menu in settings. and select allow oem unlocking and usb debugging.<br />
3. if not leave it... go on and connect your phone to the PC while in fastboot mode.<br />
<br />
BUT, before that: open Command prompt on your PC. (search it on the search box). right click on it and open it in administrator mode. <br />
type in: bcdedit /set testsigning on <br />
hit enter and restart your pc<br />
(this is imp.)<br />
<br />
4. open the zip file and extract the contents. open the boot edl mode folder and click the edl.bat file. allow it to run.<br />
5. now screen will turn black, do not disturb it. Now flash the twrp by running flash twrp.bat from the 'flash TWRP' folder.<br />
6. Now go to Unlock folder and run the unlock bootloader.bat file.<br />
your phone will boot into the TWRP recovery mode automatically.<br />
if it opens in chineese you select every tab and find the globe icon. <br />
if the globe icon is found on any of the tab select it and change the language to ENGLISH.<br />
<br />
wipe your system from the wipe tab:<br />
Now download the latest CM13 SNAPSHOT BUILD ROM FOR YOUR REDMI:<br />
https://download.cyanogenmod.org/get/kenzo-snapshot.zip<br />
and GAPPS:<br />
http://opengapps.org/?api=6.0&variant=mini<br />
do select the arm 64 version and mini one.<br />
<br />
download from your pc and copy it to micro sd card. enter this card into you phone and go to mount in twrp. <br />
mount the micro sd card storage.<br />
select the zip file on the micro sd card from the install tab on twrp and flash it.<br />
now go back and flash open gapps zip file.<br />
<br />
now REBOOT to system. everything will work fine....
Sent from my ASUS_T00J using Tapatalk
---------- Post added at 12:01 AM ---------- Previous post was at 12:00 AM ----------
The above is useful try it
Sent from my ASUS_T00J using Tapatalk

Related

Can't debug [INSTALL_FAILED_INVALID_APK]

I have a sola, running the JB port from munjeni.
I'm devlopping an app and I get
Failure [INSTALL_FAILED_INVALID_APK] when trying to debug on the phone. USB debug activated of course.
I see this message as well DeviceMonitor: Adb rejected connection to client '21134': closed
My Nexus 7 when i did that, aksed me to autorize my PC. It seem the sola just deny acces ?
Is that some problem with the JB port ? Common problem with the sola ?? Invalid apk, not really a usefull message.
I'm using intelliJ, and here is the manifest, just in case :
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.MyLauncher"
android:versionCode="1"
android:versionName="1.0">
<uses-sdk android:minSdkVersion="14"/>
<application android:label="@string/app_name" android:icon="@drawable/ic_launcher">
<activity android:name="LauncherScreen" android:theme="@android:style/Theme.Wallpaper.NoTitleBar.Fullscreen">
android:label="@string/app_name">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.HOME" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
</activity>
</application>
</manifest>
I did some test, put akp on SD, install, start -> all OK.
So apk is valid for sure, and compatible. Had to be some securitty thing bloking it.
EowynCarter said:
I did some test, put akp on SD, install, start -> all OK.
So apk is valid for sure, and compatible. Had to be some securitty thing bloking it.
Click to expand...
Click to collapse
Did you solve?
Yes, got myself a nexus 4
Joke aside, look around in the developer setting, at adb and all.
And the max / min sdk version.
You might also want to try adb install name.akp see what happens.
What phone and rom are you using exactly?
EowynCarter said:
Yes, got myself a nexus 4
Joke aside, look around in the developer setting, at adb and all.
And the max / min sdk version.
You might also want to try adb install name.akp see what happens.
What phone and rom are you using exactly?
Click to expand...
Click to collapse
No way....same extact error with adb install.
My phone is a Zopo zp998 with rom of 28/3/2014
Before the rom update it was working fine!

XT912 brick

Good day everyone! I would like to ask some help..
I'm actually noob in motorolla droid and this is my first motorolla phone ever. lol
Yesterday my brother gave me this XT912 since he got a new phone.
One of his colleagues rooted and changed the ROM to ECLIPSE 1.5.1 and it's running Android ICS 4.0.4 firmware.
When he gave the phone to me, I couldn't install some applications more specifically google hangouts coz it gives me an error:
E: signature verification failed
I downloaded the ff. firmwares from this site http://sbf.droid-developers.org/phone.php?device=9
Android 4.1.2 Blur_Version.98.72.165.XT912.Verizon.en.US
Android 4.1.2 Blur_Version.98.72.16.XT912.Verizon.en.US
Android 4.0.4 Blur_Version.6.16.211.XT912.Verizon.en.US
flashed them using the custom recovery option from the device (hold vol - & vol + keys while android logo appears) but eventually it gave me an error:
signature verification failed installation aborted
After series of google search I found this post by matt : http://www.droidrzr.com/index.php/t...xt912-jellybean-windows-mac-linux-all-in-one/
But it made my situation worst
Downloaded the latest version, DroidRAZRUtility1.82 Jellybean.
Installed the drivers for 32bit since I'm running W7 32bit OS.
Ran the WindowsUtility.bat and chose option 1 to completely wipe and install JB.
After running the utility I cannot boot up to recovery and normal boot-up anymore. In other words, it bricked my XT912.
It gave me this error:
When in AP Fastboot Mode:
AP Fastboot Flash Mode (S) (Flash Failure)
0A.74
eMMC Info: Size 16G
To return to normal mode - first press power key to power down
Device is LOCKED. Status Code:0
Battery OK
OK to Program
Connect USB
Data Cable
---------------------------
When in Normal Bootup and Recovery:
Invalid Flash Mode (S) (Boot Failure)
0A.74
eMMC Info: Size 16G
To return to normal mode - first press power key to power down
Device is LOCKED. Status Code:0
Invalid CG OTV (CG: system): Invalid SP Data
Invalid CD Version (CG: system)
Invalid CG OTV (CG: system)
As another try, I used Motorola RSD Lite 6.1.5 + MTK Patch and tried using the fastboot files (firmwares) that I downloaded earlier:
Android 4.1.2 Blur_Version.98.72.165.XT912.Verizon.en.US
Android 4.1.2 Blur_Version.98.72.16.XT912.Verizon.en.US
Android 4.0.4 Blur_Version.6.16.211.XT912.Verizon.en.US
But it gave me this error:
Failed flashing process. 6/16 flash motoboot "motoboot.img" -> Phone returned FAIL.
I really don't know how to fix this.. I really need your help guys...
Thanks,
Josh
Hi Josh,
Sorry to hear that....first of all, can you access fastboot mode? or you cant do absolutly anithing with the droid?
joshua3001 said:
Hi Josh,
Sorry to hear that....first of all, can you access fastboot mode? or you cant do absolutly anithing with the droid?
Click to expand...
Click to collapse
Hi joshua3001,
Yes, I could still boot in to fastboot mode.
joswa said:
When in Normal Bootup and Recovery:
Invalid Flash Mode (S) (Boot Failure)
0A.74
eMMC Info: Size 16G
To return to normal mode - first press power key to power down
Device is LOCKED. Status Code:0
Invalid CG OTV (CG: system): Invalid SP Data
Invalid CD Version (CG: system)
Invalid CG OTV (CG: system)
As another try, I used Motorola RSD Lite 6.1.5 + MTK Patch and tried using the fastboot files (firmwares) that I downloaded earlier:
Android 4.1.2 Blur_Version.98.72.165.XT912.Verizon.en.US
Android 4.1.2 Blur_Version.98.72.16.XT912.Verizon.en.US
Android 4.0.4 Blur_Version.6.16.211.XT912.Verizon.en.US
But it gave me this error:
Failed flashing process. 6/16 flash motoboot "motoboot.img" -> Phone returned FAIL.
I really don't know how to fix this.. I really need your help guys...
Thanks,
Josh
Click to expand...
Click to collapse
Are you trying to flash all three of these at the same time?
You won't be able to flash the 4.0.4 firmware, you are obviously already on the JB kernel(4.1.2), so you won't be able to go back to ICS(4.0.4)
That is what the screenshot you provided is telling you. The firmware it is failing on is the 4.0.4
You need to choose ONE of the 4.1.2 firmwares and flash it via RSD lite. Make sure you have plenty of battery when you do it.
Draxin is right dude, you cant flash all of them, i wll recomend you to flash JUST the .165 ...let me now (Y)
have the same problem
Draxin said:
Are you trying to flash all three of these at the same time?
You won't be able to flash the 4.0.4 firmware, you are obviously already on the JB kernel(4.1.2), so you won't be able to go back to ICS(4.0.4)
That is what the screenshot you provided is telling you. The firmware it is failing on is the 4.0.4
You need to choose ONE of the 4.1.2 firmwares and flash it via RSD lite. Make sure you have plenty of battery when you do it.
Click to expand...
Click to collapse
Hi Draxin,
I am having the same problem with my XT912 as well.
I have tried both the 4.1.2 options available at http://sbf.droid-developers.org/phone.php?device=9 and i am getting different errors with both of them.
For one i am getting flashcdt.bin 'cdt.bin_signed' > Phone returned Fail and for the other one i am getting Failed flashing process: 6/16 flash motoboot 'motoboot.img'' Phone returned Fail.
Can you please help?
I have been trying different things now and nothing is really working with my phone
need help please
joshua3001 said:
Draxin is right dude, you cant flash all of them, i wll recomend you to flash JUST the .165 ...let me now (Y)
Click to expand...
Click to collapse
Hi ,
I am having the same problem with my XT912 as well.
I have tried both the 4.1.2 options available at http://sbf.droid-developers.org/phone.php?device=9 and i am getting different errors with both of them.
For one i am getting flashcdt.bin 'cdt.bin_signed' > Phone returned Fail and for the other one i am getting Failed flashing process: 6/16 flash motoboot 'motoboot.img'' Phone returned Fail.
Can you please help?
I have been trying different things now and nothing is really working with my phone
nishanchi said:
Hi Draxin,
I am having the same problem with my XT912 as well.
I have tried both the 4.1.2 options available at http://sbf.droid-developers.org/phone.php?device=9 and i am getting different errors with both of them.
For one i am getting flashcdt.bin 'cdt.bin_signed' > Phone returned Fail and for the other one i am getting Failed flashing process: 6/16 flash motoboot 'motoboot.img'' Phone returned Fail.
Can you please help?
I have been trying different things now and nothing is really working with my phone
Click to expand...
Click to collapse
Hello,
Well regardless I would stick with the .165. Did you make sure debugging was enabled before trying to flash with RSD Lite? Did you make sure your phone was connected as a mass storage device?
Another option is Matt's Utility Make sure to follow his directions and thank him.
Same issue plz help me...
joswa said:
Good day everyone! I would like to ask some help..
I'm actually noob in motorolla droid and this is my first motorolla phone ever. lol
Yesterday my brother gave me this XT912 since he got a new phone.
One of his colleagues rooted and changed the ROM to ECLIPSE 1.5.1 and it's running Android ICS 4.0.4 firmware.
When he gave the phone to me, I couldn't install some applications more specifically google hangouts coz it gives me an error:
E: signature verification failed
I downloaded the ff. firmwares from this site http://sbf.droid-developers.org/phone.php?device=9
Android 4.1.2 Blur_Version.98.72.165.XT912.Verizon.en.US
Android 4.1.2 Blur_Version.98.72.16.XT912.Verizon.en.US
Android 4.0.4 Blur_Version.6.16.211.XT912.Verizon.en.US
flashed them using the custom recovery option from the device (hold vol - & vol + keys while android logo appears) but eventually it gave me an error:
signature verification failed installation aborted
After series of google search I found this post by matt : http://www.droidrzr.com/index.php/t...xt912-jellybean-windows-mac-linux-all-in-one/
But it made my situation worst
Downloaded the latest version, DroidRAZRUtility1.82 Jellybean.
Installed the drivers for 32bit since I'm running W7 32bit OS.
Ran the WindowsUtility.bat and chose option 1 to completely wipe and install JB.
After running the utility I cannot boot up to recovery and normal boot-up anymore. In other words, it bricked my XT912.
It gave me this error:
When in AP Fastboot Mode:
AP Fastboot Flash Mode (S) (Flash Failure)
0A.74
eMMC Info: Size 16G
To return to normal mode - first press power key to power down
Device is LOCKED. Status Code:0
Battery OK
OK to Program
Connect USB
Data Cable
---------------------------
When in Normal Bootup and Recovery:
Invalid Flash Mode (S) (Boot Failure)
0A.74
eMMC Info: Size 16G
To return to normal mode - first press power key to power down
Device is LOCKED. Status Code:0
Invalid CG OTV (CG: system): Invalid SP Data
Invalid CD Version (CG: system)
Invalid CG OTV (CG: system)
As another try, I used Motorola RSD Lite 6.1.5 + MTK Patch and tried using the fastboot files (firmwares) that I downloaded earlier:
Android 4.1.2 Blur_Version.98.72.165.XT912.Verizon.en.US
Android 4.1.2 Blur_Version.98.72.16.XT912.Verizon.en.US
Android 4.0.4 Blur_Version.6.16.211.XT912.Verizon.en.US
But it gave me this error:
Failed flashing process. 6/16 flash motoboot "motoboot.img" -> Phone returned FAIL.
I really don't know how to fix this.. I really need your help guys...
Thanks,
Josh
Click to expand...
Click to collapse
I have same issue in RSD and it always fails in motoboot.img
please give me solution
 @xda -developers @Razr MAXX
NabeelSaleem said:
I have same issue in RSD and it always fails in motoboot.img
please give me solution
@xda -developers @Razr MAXX
Click to expand...
Click to collapse
Windows version?
Rsd lite version?
Firmware version?
Bootloader version?
Sent from my XT894 using Tapatalk
sd_shadow said:
Windows version?
Rsd lite version?
Firmware version?
Bootloader version?
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
Thanks for reply
windows 8.1 pro
RSD 6.1.5
versions is tried:
VRZ_XT912_9.8.2O-72_VZW-16-5_1FF.xml
VRZ_XT912_6.7.2-180_DHD-16_M4-31_1FF.xml
and what is bootloader version? where can i find this?
NabeelSaleem said:
Thanks for reply
windows 8.1 pro
RSD 6.1.5
versions is tried:
VRZ_XT912_9.8.2O-72_VZW-16-5_1FF.xml
VRZ_XT912_6.7.2-180_DHD-16_M4-31_1FF.xml
and what is bootloader version? where can i find this?
Click to expand...
Click to collapse
AP Fastboot screen has bootloader version.
Windows 8 doesn't work well with rsd lite
Sent from my XT894 using Tapatalk
sd_shadow said:
AP Fastboot screen has bootloader version.
Windows 8 doesn't work well with rsd lite
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
It's written
AP Fastboot Flash Mode (S)
0A.77
eMMC Info: size 16g
should i use windows 7?
and what about xml versions? are they ok
NabeelSaleem said:
It's written
AP Fastboot Flash Mode (S)
0A.77
eMMC Info: size 16g
should i use windows 7?
and what about xml versions? are they ok
Click to expand...
Click to collapse
Window 7 is a better option.
verifiy Moto driver are installed.
try RSDLite 6.2.4
0A.77 means only Jellybean firmware can be used.
This is latest
4.1.2 Verizon US 9.8.2O-72_VZW-16-5
614 MB (644,076,403 bytes)
Md5: 410F338706C1AD599E839DDE4FD60A23
cdma_spyder_9.8.2O-72_VZW-16-5_cfc.xml
Verify md5 checksum for firmware
also the DROID RAZR Utility XT912 Jellybean UPDATED is a good option
sd_shadow said:
Window 7 is a better option.
verifiy Moto driver are installed.
try RSDLite 6.2.4
0A.77 means only Jellybean firmware can be used.
This is latest
4.1.2 Verizon US 9.8.2O-72_VZW-16-5
614 MB (644,076,403 bytes)
Md5: 410F338706C1AD599E839DDE4FD60A23
cdma_spyder_9.8.2O-72_VZW-16-5_cfc.xml
Verify md5 checksum for firmware
also the DROID RAZR Utility XT912 Jellybean UPDATED is a good option
Click to expand...
Click to collapse
Can you give me link for this firmware or this one correct > http://motofirmware.center/files/file/44-vrz_xt912_982o-72_vzw-16-5_cfcxmlzip/
size is 614.2MB
and what is Md5 and cdma lines you wrote? how can i check them?
and really thanks for your help... please guide me these things too ...
NabeelSaleem said:
Can you give me link for this firmware or this one correct > http://motofirmware.center/files/file/44-vrz_xt912_982o-72_vzw-16-5_cfcxmlzip/
size is 614.2MB
and what is Md5 and cdma lines you wrote? how can i check them?
and really thanks for your help... please guide me these things too ...
Click to expand...
Click to collapse
See Moto Drivers, RSD Lite, and other Unbricking Tools
http://forum.xda-developers.com/general/rooting-roms/motorola-usb-drivers-rsd-lite-firmware-t3042687
Sent from my XT894 using Tapatalk
sd_shadow said:
See Moto Drivers, RSD Lite, and other Unbricking Tools
http://forum.xda-developers.com/general/rooting-roms/motorola-usb-drivers-rsd-lite-firmware-t3042687
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
I know this and i downloaded RSD lite 6.2.4
Installed moto drivers
also checked razr utility tool
I downloaded firmware as you said but in my laptop its also failed to flash with this firmware > http://motofirmware.center/files/file/44-vrz_xt912_982o-72_vzw-16-5_cfcxmlzip/
and here is XML code
Code:
<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="SPYDER_CFC" />
<software_version version="9.8.2O-72_VZW-16-5" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="flash" partition="cdt.bin" filename="cdt.bin_signed" MD5="D9F76350C7A9694FEA32D84AF1C4AA39" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="emstorage" filename="emstorage.img" MD5="081640654B9F45CD31C3903180A72BD1" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="mbm" filename="allow-mbmloader-flashing-mbm.bin" MD5="55D703D1D8D8631F31BE89A6069AD68E" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="mbmloader" filename="mbmloader.bin" MD5="42F7110DE49D6D28EA0540F1C02F9F1B" />
<step operation="flash" partition="mbm" filename="mbm.bin" MD5="F541F64F56739D65C19557E33F8AEF3C" />
<step operation="oem" var="fb_mode_set" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="D25F83E68E3BD76AE7F9405581E49B41" />
<step operation="reboot-bootloader" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="erase" partition="userdata" />
<step operation="flash" partition="logo.bin" filename="logo.bin" MD5="CD111CC7B675E62A7D85A50632FB88E8" />
<step operation="flash" partition="devtree" filename="device_tree.bin" MD5="04E2F24447783A0FF32E86E0DCA1D0C0" />
<step operation="flash" partition="system" filename="system.img" MD5="923FC8E9A3848744EACC8E98BE43DABE" />
<step operation="flash" partition="boot" filename="boot.img" MD5="D89B288A78E43CDAAFA55B6545A2FAEA" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="E8CA4889CF1DC7236526F628D2FCF948" />
<step operation="flash" partition="cdrom" filename="cdrom" MD5="FD1D40C2B40F0222EB8EF98AEB3AA87C" />
<step operation="flash" partition="preinstall" filename="preinstall.img" MD5="619C6B45BBB62D13FD272A22DD19D63C" />
<step operation="flash" partition="radio" filename="radio.img" MD5="596BA902DB1F52CD97DC0466B2C88E24" />
<step operation="oem" var="fb_mode_clear" />
</steps>
</flashing>
flash fails on cdt.bin ... please tell me what to do @sd_shadow
NabeelSaleem said:
I know this and i downloaded RSD lite 6.2.4
Installed moto drivers
also checked razr utility tool
I downloaded firmware as you said but in my laptop its also failed to flash with this firmware > http://motofirmware.center/files/file/44-vrz_xt912_982o-72_vzw-16-5_cfcxmlzip/
and here is XML code
Code:
<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="SPYDER_CFC" />
<software_version version="9.8.2O-72_VZW-16-5" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="flash" partition="cdt.bin" filename="cdt.bin_signed" MD5="D9F76350C7A9694FEA32D84AF1C4AA39" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="emstorage" filename="emstorage.img" MD5="081640654B9F45CD31C3903180A72BD1" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="mbm" filename="allow-mbmloader-flashing-mbm.bin" MD5="55D703D1D8D8631F31BE89A6069AD68E" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="mbmloader" filename="mbmloader.bin" MD5="42F7110DE49D6D28EA0540F1C02F9F1B" />
<step operation="flash" partition="mbm" filename="mbm.bin" MD5="F541F64F56739D65C19557E33F8AEF3C" />
<step operation="oem" var="fb_mode_set" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="D25F83E68E3BD76AE7F9405581E49B41" />
<step operation="reboot-bootloader" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="erase" partition="userdata" />
<step operation="flash" partition="logo.bin" filename="logo.bin" MD5="CD111CC7B675E62A7D85A50632FB88E8" />
<step operation="flash" partition="devtree" filename="device_tree.bin" MD5="04E2F24447783A0FF32E86E0DCA1D0C0" />
<step operation="flash" partition="system" filename="system.img" MD5="923FC8E9A3848744EACC8E98BE43DABE" />
<step operation="flash" partition="boot" filename="boot.img" MD5="D89B288A78E43CDAAFA55B6545A2FAEA" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="E8CA4889CF1DC7236526F628D2FCF948" />
<step operation="flash" partition="cdrom" filename="cdrom" MD5="FD1D40C2B40F0222EB8EF98AEB3AA87C" />
<step operation="flash" partition="preinstall" filename="preinstall.img" MD5="619C6B45BBB62D13FD272A22DD19D63C" />
<step operation="flash" partition="radio" filename="radio.img" MD5="596BA902DB1F52CD97DC0466B2C88E24" />
<step operation="oem" var="fb_mode_clear" />
</steps>
</flashing>
flash fails on cdt.bin ... please tell me what to do @sd_shadow
Click to expand...
Click to collapse
Does your device have Verizon on front and back?
Sent from my XT894 using Tapatalk
---------- Post added at 07:36 AM ---------- Previous post was at 07:33 AM ----------
How to use md5
http://forum.xda-developers.com/showthread.php?t=
Sent from my XT894 using Tapatalk
sd_shadow said:
Does your device have Verizon on front and back?
Sent from my XT894 using Tapatalk
---------- Post added at 07:36 AM ---------- Previous post was at 07:33 AM ----------
How to use md5
http://forum.xda-developers.com/showthread.php?t=
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
Yes written on both side.
4g LTE verizon
NabeelSaleem said:
Yes written on both side.
4g LTE verizon
Click to expand...
Click to collapse
What is complete text on AP Fastboot Flash Mode screen?

[Q&A] [APP][2.2+][ROOT][WiFi] Reaver-GUI for Android

Q&A for [APP][2.2+][ROOT][WiFi] Reaver-GUI for Android
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [APP][2.2+][ROOT][WiFi] Reaver-GUI for Android. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
bcmon not insalled
Good day sir(s)
i cant install bcmon it says app not installed
my phone is asus zenfone 4 A400CG
help :crying: :crying: :crying:
It is compatible with galaxy s5?
Sent from my SM-G900F using XDA Free mobile app
please help me
i am open this and start rfa and enable monitor mode,
one error is syntax for scipt send me scipt use android device is 4.2.2 xolo q700
bcmon problame
i have same problame for bcmon
firmware model :not detected
installed tools verion :0
installed fw version :0
i m using xperia l
with lolipop 5.0.2 cyanogen 12
i9100 CM12 RFA BCMON
Hello,
I have installed today Cyanogen Mod 12.1-20150423 to my Samsung Galaxy S2 phone. I would like to try RFA, so I installed bcmon. Mostly it crashes on start up. When not it says "monitor mode enable - Failed" when tapped on Enable monitor mode. RFA won't start an attack. It says "Enabled monitor-mode succesfully on", but that's all ... Nothing else happens ...
Any advice will be appriciated. Thanks
RFA on CM12
Hi there, yesterday I was trying to get it running whole day .. Without result ...
Well, so I rolled back to CM10.1.3 (i am on SGS2 i9100) and it goes without any problem. (Technically) Even the system is stable and running withou any problem.
I am just stuck on "Detected AP rate limiting, waiting 60 secs..." after starting an attack. Do you guys have any solution for this ? I already tried to increase timeouts, but that did not help.
Thanks in advance for any advice
I get a libpcap .so.1 error, dont have a bcmon device
Why I got this message?
gusky651 said:
I get a libpcap .so.1 error, dont have a bcmon device
Click to expand...
Click to collapse
can u upload libpcap.so library file here..
Hey , i downloaded rfa and bcmon , but it shows :
firmware model is not detected, install tools version:0; installed fw version:0
Nothing works , settings doesnt open and if i click on status , it crashes
Sent from my Micromax AQ4501 using XDA Free mobile app
--------------
kyzinet said:
Hi there, yesterday I was trying to get it running whole day .. Without result ...
Well, so I rolled back to CM10.1.3 (i am on SGS2 i9100) and it goes without any problem. (Technically) Even the system is stable and running withou any problem.
I am just stuck on "Detected AP rate limiting, waiting 60 secs..." after starting an attack. Do you guys have any solution for this ? I already tried to increase timeouts, but that did not help.
Thanks in advance for any advice
Click to expand...
Click to collapse
You did everything right, it’s just the AP which is protected against this kind of attack. Just find another one to test.
start up script for reaver
I been having a problem with the start script I put it in my com.bcom.bcom/files folder but every time I try to use the activation script it says no such file exist and I can't open monitor mode I have a galaxy s5 any help would be great thank you
I use script, my phone htc one e8 chipset snapdragon 801
There is an error
Firmware model not detected
Installed tools version 0
Installed fw version 0
I am using xiaomi redmi 1s help me
Bro agr mera wifi kisi se connect h to mai uska password dekh skta hu bt usne change kr diya to kya koi trick h pta krne ki?????
Plz telll
Does it really work on lollipop...?
If not any other tools that can replace it..i mean for bcmon
Does Xperia Z3 has this bcm4329/4330 wifi chipset?
Wysłane z mojego D6603 przy użyciu Tapatalka
[quote name="SOEDI" post=45882817]
<br />
<b>Reaver for Android v1.30</b><br />
<i>Reaver-WPS GUI for rooted devices with bcm4329/4330 wifi chipset or working external wifi card.</i><br />
<br />
<br />
<br />
<b>INFO:</b><br />
Reaver for Android, short RfA, is a simple-to-use Reaver-GUI for Android devices with monitor-mode support.<br />
It has some very cool features:<br />
<br />
<b><br />
* Detects automatically WPS-enabled routers.<br />
* All Reaver-Settings are accessible from a simple-to-use GUI.<br />
* Activates and deactivates Monitor-Mode automatically when needed.<br />
* Provides a simple way to connect when Reaver finds the WPA-Key.<br />
* External script support<br />
</b><br />
<br />
<b>Project status: PRE-FINAL</b><blockquote><i>What does this mean?</i><br />
There are some features which are not implemented yet.<br />
Developement will continue very soon.</blockquote><br />
<b>Installation</b><br />
<br />
1. Download/install bcmon.apk from HERE and RfA.apk from the bottom of this post. RfA may also download bcmon automatically.<br />
2. Run bcmon, if it crashes try a second time.<br />
3. If all runs fine, start RfA. If not, your device may be not bcmon compatible. Please see second post.<br />
4. After selecting an WPS-enabled router, click on "Test Monitor-Mode".<br />
5. Now you can use RfA, don't uninstall bcmon.<br />
<br />
Steps 1 - 4 are only for the installation, they don't have to be repeated once done.<br />
<br />
<br />
<b>FAQ:</b><br />
<blockquote><b><i>What is this awesome app actually usefull for?</i></b><br />
Well, RfA is able to unveil the actual WPA(2)-Key of many routers within 2 - 10 hours.<br />
<br />
<b><i>WHAT?! I though WPA(2) is safe?</i></b><br />
It used to be, but then many router models got WiFi Protected Setup, short WPS, implemeted, which is pretty vulnerable. (Details)<br />
Basically it's a Brute-Force attack with Reaver against a 8 digit pin with 10^4 + 10^3 possibilities.<br />
<br />
<b><i>What is Reaver?</i></b><br />
Reaver-WPS is a pentesting tool developed by Tactical Network Solutions.<br />
It attacks WPS-enabled routers and after the WPS-Pin is cracked, it retrieves the actual WPA-key.<br />
Reaver provides only a terminal interface, which is ok for notebooks etc., however it's a pain on Android devices.<br />
Because of this I developed RfA.<br />
<br />
<b><i>Doesn't Reaver requires monitor-mode and so can't work on Android?</i></b><br />
Yes, Reaver needs monitor-mode, but thanks to bcmon (or external wifi cards) some Android devices are now monitor-mode capable.</blockquote><br />
<b>bcmon compatibility</b><blockquote><b>Developed and tested on:</b> Nexus 7 2012 (Stock 4.3)<br />
RfA *should* work on all devices with bcmon support (Broadcom bcm4329/bcm4330 chipsets)<br />
Simply try by installing bcmon. Don't worry, if something goes wrong a simple reboot should fix everything.<br />
For external wifi cards please see second post.<br />
<br />
<b>Tested & works on:</b><br />
Nexus 7 2012 (Stock 4.3, Cyanogen 9)<br />
Huawei Honour (Cyanogen Mod based ROM)<br />
<br />
<b>bcmon does NOT work on:</b><br />
Samsung Galaxy S3/4/5<br />
HTC One<br />
LG G2<br />
Nexus 4/5<br />
Nexus 7 (2013)<br />
</blockquote><b>Credits & used tools:</b><br />
<blockquote><b>Monitor-Mode over bcmon.apk:</b><br />
Omri Ildis, Ruby Feinstein & Yuval Ofir<br />
See: bcmon.blogspot.com<br />
<br />
<b>Reaver-WPS:</b><br />
Tactical Network Solutions<br />
See: code.google.com/p/reaver-wps/</blockquote><b>Disclaimer</b><br />
<blockquote><b><font color="Red">Attention: Hacking of networks is illegal without having the permission of the owner! The developer is not responsible for any damage etc. this app could cause.<br />
This software is only intended to show a big security hole, not to be able to surf in the neighbours Wifi</font></b></blockquote><b><u>XDAevDB Information</u></b><br />
<b>Reaver-GUI for Android, App for all devices (see above for details)</b><br />
<br />
<b><u>Contributors</u></b><br />
SOEDI, bcmon team & Tactical Network Solutions<br />
<br />
<b><u>Version Information</u></b><br />
<b>Status:</b> Stable<br />
<b>Current Stable Version:</b> 1.30<br />
<b>Stable Release Date:</b> 2014-07-01<br />
<b>Beta Release Date:</b> 2013-11-04<br />
<br />
<b>Created</b> 2013-09-24<br />
<b>Last Updated</b> 2014-09-27[/QUOTE]<br />
Good News<br />
Guys I have found pixiwps Good binary for android . You have to copy the binary and past in data/data/com.bcmom.bcmon/files/tools the link is<br />
http://wpspin.blogspot.in/?m=1<br />
I was unable to download cuz of ads if some one could dowanload and put the file it will be really a great help for me from you tnx in advance<br />
<br />
Sent from my GT-I9070 using XDA-Developers mobile app<br />
---------------<br />
<b>Admin Note: this thread has a dedicated questions and answers section which you can access here -->.</b>
Sent from my GT-I9070 using XDA-Developers mobile app
Installed tools through bcmon.
(Succeed)
ENABLE MONITOR MODE
(FAILED)
WENT TO REAVER AND UNCHECKED USE BCMON
Made scripts /selected and saved them
(Start monitor mode from reaver)
Sorry activate.sh [start script] not found.
Checked use bcmon again..
ENABLE MONITOR MODE FROM REAVER.
SUCCEEDED
MONITOR MODE ENABLED
START ATTACK
STARTING...
SWITCHING WILAN0 TO CHANNEL 1
STUCK 4 TWO HOURS
 @SOEDI
Any solution, sir?

[Q] xt910 black screen after motorola logo

hi everyone,
first of all i tried search same problem but there is different i can enter to AP fastboot and can goes in to recovery press power +up+down
( i have installed on my xt910 cm 11 (4.4.4) using safestrap 3.65 after the offical 5.0.2 rom cm12 come out (http://forum.xda-developers.com/droid-razr/development/rom-cyanogenmod-12-0-t2950906)
i update safestrap to 3.75 then uninstall recovery then reinstall it reboot
delete rom slot and re install now one and then install 5.0.2 rom +gapp reboot (take about 10 min ) and then setup steps goes fine but the Device became annoyingly slow so I tried
to delete rom slot again but this time i select rom slot 2 and wipe then install 5.0.2 rom +gapp then reboot )
motorola logo Appears then no thing black screen actually black light screen (there is no safestrap logo Appear)
i tried ap fastboot and thats what i got
battery low
cannot program
connect usb
data cable
cant charge battry any more dont know why
i can go to recovry by press power +up+down
but every time i tried to install (( cm11 4.4.4)) i got install field
thanks and sorry for bad english XD
Abdoobood said:
hi everyone,
first of all i tried search same problem but there is different i can enter to AP fastboot and can goes in to recovery press power +up+down
( i have installed on my xt910 cm 11 (4.4.4) using safestrap 3.65 after the offical 5.0.2 rom cm12 come out (http://forum.xda-developers.com/droid-razr/development/rom-cyanogenmod-12-0-t2950906)
i update safestrap to 3.75 then uninstall recovery then reinstall it reboot
delete rom slot and re install now one and then install 5.0.2 rom +gapp reboot (take about 10 min ) and then setup steps goes fine but the Device became annoyingly slow so I tried
to delete rom slot again but this time i select rom slot 2 and wipe then install 5.0.2 rom +gapp then reboot )
motorola logo Appears then no thing black screen actually black light screen (there is no safestrap logo Appear)
i tried ap fastboot and thats what i got
battery low
cannot program
connect usb
data cable
cant charge battry any more dont know why
i can go to recovry by press power +up+down
but every time i tried to install (( cm11 4.4.4)) i got install field
thanks and sorry for bad english XD
Click to expand...
Click to collapse
Try
Power off, Hold volume buttons (or M key/droid 4), Power on, release buttons at
Boot Mode Selection Menu> Scroll down with volume down button, to BP Tools, Select with Volume UP button, should boot directly to SafeStrap (if it's still there).
Or Try
Booting from AP fastboot to charging mode
If the Device will only boot to AP Fastboot and it says Battery Low
Connect the phone/Device ato a Wall Charger (not PC)
-In AP Fastboot Mode hold Volume down& power buttons at the same time for +10 seconds
- When screen goes black...release power button
-Then IMMEDIATELY press and hold Vol - and Vol+ to boot to Boot Menu.
- In Boot Menu scroll down with volume down to BP Tools, press volume up to select
- Device should boot to Charging Mode with battery icon
- Once battery is charged, try flashing in AP Fastboot again
This will only work if battery charging Firmware is still preset and not corrupted
If Motorola Device will not boot to Charging Mode, a Fastboot cable will be needed.
http://goo.gl/QllP1j
{
"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"
}
Sent from my XT907 using Tapatalk
sd_shadow said:
Try
Power off, Hold volume buttons (or M key/droid 4), Power on, release buttons at
Boot Mode Selection Menu> Scroll down with volume down button, to BP Tools, Select with Volume UP button, should boot directly to SafeStrap (if it's still there).
Or Try
Booting from AP fastboot to charging mode
If the Device will only boot to AP Fastboot and it says Battery Low
Connect the phone/Device ato a Wall Charger (not PC)
-In AP Fastboot Mode hold Volume down& power buttons at the same time for +10 seconds
- When screen goes black...release power button
-Then IMMEDIATELY press and hold Vol - and Vol+ to boot to Boot Menu.
- In Boot Menu scroll down with volume down to BP Tools, press volume up to select
- Device should boot to Charging Mode with battery icon
- Once battery is charged, try flashing in AP Fastboot again
This will only work if battery charging Firmware is still preset and not corrupted
If Motorola Device will not boot to Charging Mode, a Fastboot cable will be needed.
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
I done this before but battry still low so how can i make cable i cant buy cable cus i live in egypt and there is no motorola suports there
Can u plz Explain to me how to make 1 in easy Easy Language
Thanks alot for ur time
edit: http://goo.gl/1glUry
sd_shadow said:
edit:
Click to expand...
Click to collapse
ok dude i got batrry ok
ok to program
conect usb
date cable
rsd lite 6.1.6 cant fine my xt910
is there any driver should i install or something
i got the sound on my pc (usb connected sound)
but rsd cant find my phone
thank you $_$
Abdoobood said:
ok dude i got batrry ok
ok to program
conect usb
date cable
rsd lite 6.1.6 cant fine my xt910
is there any driver should i install or something
i got the sound on my pc (usb connected sound)
but rsd cant find my phone
thank you $_$
Click to expand...
Click to collapse
Download and Install Drivers (Motorola_End_User_Driver_Installation...)
Motorola Drivers for Windows http://goo.gl/mIsi4h
It’s a good idea to reboot pc after installing drivers
Sent from my XT907 using Tapatalk
sd_shadow said:
Download and Install Drivers (Motorola_End_User_Driver_Installation...)
Motorola Drivers for Windows
It’s a good idea to reboot pc after installing drivers
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
XD ok the pc fine my xt910 when i press start
rsdlite is stoping at step 1 and i got
failed flashing process. 1/19 flash mbm "allow-mbmloader-flashing-mbm.bin" -> usb error occurred while reading/writing
my fastboot 0a.74
i use 9.8.2O-124_SPUEM-14_S7_USASPDRICS01RUKE1007.0R_USASPDRJBRTGB_P011_b57374ab5a_p2b_S1FF_fb_CFC.xml
win8-64bit
last version :5.0.1 cm12
but i think there is no more system in phone cuz i got black screen after motorola logo
I'm sorry for being annoying and thank you very much
Abdoobood said:
XD ok the pc fine my xt910 when i press start
rsdlite is stoping at step 1 and i got
failed flashing process. 1/19 flash mbm "allow-mbmloader-flashing-mbm.bin" -> usb error occurred while reading/writing
my fastboot 0a.74
i use 9.8.2O-124_SPUEM-14_S7_USASPDRICS01RUKE1007.0R_USASPDRJBRTGB_P011_b57374ab5a_p2b_S1FF_fb_CFC.xml
win8-64bit
last version :5.0.1 cm12
but i think there is no more system in phone cuz i got black screen after motorola logo
I'm sorry for being annoying and thank you very much
Click to expand...
Click to collapse
bootloader 0A.74 should just be ICS, so you should be able to use a ICS or Jellybean stock XML file
fail at flashing-mbm.bin" is likely that stock XML file is for a different carrier/region that what is currently on device
what carrier do you use, what country?
sd_shadow said:
bootloader 0A.74 should just be ICS, so you should be able to use a ICS or Jellybean stock XML file
fail at flashing-mbm.bin" is likely that stock XML file is for a different carrier/region that what is currently on device
what carrier do you use, what country?
Click to expand...
Click to collapse
I had purchased it from Saudi Arabia in the Middle East
Is there any way to know or get that from DEVICE (i mean to know what country come from)
Abdoobood said:
I had purchased it from Saudi Arabia in the Middle East
Click to expand...
Click to collapse
OK, you need to edit the .XML file
unzip/extract files
in folder will be another .XML file something like 9.8.2O-72_VZW-16-5_cfc.xml
open with notepad++
remove lines that are like
<step operation="flash" partition="cdt.bin" filename="cdt.bin_signed" MD5="D9F76350C7A9694FEA32D84AF1C4AA39" />
and
<step operation="flash" partition="radio" filename="radio.img" MD5="596BA902DB1F52CD97DC0466B2C88E24" />
do not leave empty line
save the changes in notepad++ and close notepad++
in RSD Lite make sure you select the unzipped .XML
Windows 8? A lot of people has problems with Windows 8,find somewhere Windows 7.
Sent from my Razr XT910
sd_shadow said:
OK, you need to edit the .XML file
unzip/extract files
in folder will be another .XML file something like 9.8.2O-72_VZW-16-5_cfc.xml
open with notepad++
remove lines that are like
<step operation="flash" partition="cdt.bin" filename="cdt.bin_signed" MD5="D9F76350C7A9694FEA32D84AF1C4AA39" />
and
<step operation="flash" partition="radio" filename="radio.img" MD5="596BA902DB1F52CD97DC0466B2C88E24" />
do not leave empty line
save the changes in notepad++ and close notepad++
in RSD Lite make sure you select the unzipped .XML
Click to expand...
Click to collapse
sorry but there is a same step name this is what xml countan
Code:
<?xml version="1.0" encoding="UTF-8"?>
<flashing>
<header>
<phone_model model="SPYDER_U" />
<software_version version="umts_spyder_mmi_emea-user 4.1.2 9.8.2O-124_SPUEM-14 1362039991 release-keysSPYDERBP_U_04.10.00R" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="flash" partition="mbm" filename="allow-mbmloader-flashing-mbm.bin" MD5="55d703d1d8d8631f31be89a6069ad68e" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="mbmloader" filename="mbmloader.bin" MD5="42f7110de49d6d28ea0540f1c02f9f1b" />
<step operation="flash" partition="mbm" filename="mbm.bin" MD5="f541f64f56739d65c19557e33f8aef3c" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="cdt.bin" filename="cdt.bin_signed" MD5="7efbcdf1bb0128b241865dab3bb50f58" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="erase" partition="emstorage" />
<step operation="flash" partition="logo.bin" filename="logo.bin" MD5="cd111cc7b675e62a7d85a50632fb88e8" />
<step operation="flash" partition="ebr" filename="ebr_signed" MD5="dfa61c2c9858a22b5fb9e53b912a44e1" />
<step operation="flash" partition="mbr" filename="mbr_signed" MD5="2600bab8703dc908168471590bb76ae8" />
<step operation="flash" partition="devtree" filename="devtree_signed" MD5="baffc70d6bfb1f60718a41ad56f1bfa2" />
<step operation="flash" partition="system" filename="system_signed" MD5="e7b648a75e897c359b26585b898ee105" />
<step operation="flash" partition="boot" filename="boot_signed" MD5="dfbf43445f5128bf692a8a97cdfa2dc5" />
<step operation="flash" partition="recovery" filename="recovery_signed" MD5="9508ac0f92d22fdeaa325f0ac5b59f7e" />
<step operation="flash" partition="cdrom" filename="cdrom_signed" MD5="f23887e8b903cce684544a981f56b0aa" />
<step operation="flash" partition="emstorage" filename="emstorage.img" MD5="f248ff87bfab03e3278891ad151adde7" />
<step operation="flash" partition="radio" filename="radio.img" MD5="611e25a2d2e132e78acdcc849754e15d" />
</steps>
</flashing>
plz edit it and re post XD
welder73 said:
Windows 8? A lot of people has problems with Windows 8,find somewhere Windows 7.
Sent from my Razr XT910
Click to expand...
Click to collapse
sd_shadow said:
OK, you need to edit the .XML file
unzip/extract files
in folder will be another .XML file something like 9.8.2O-72_VZW-16-5_cfc.xml
open with notepad++
remove lines that are like
<step operation="flash" partition="cdt.bin" filename="cdt.bin_signed" MD5="D9F76350C7A9694FEA32D84AF1C4AA39" />
and
<step operation="flash" partition="radio" filename="radio.img" MD5="596BA902DB1F52CD97DC0466B2C88E24" />
do not leave empty line
save the changes in notepad++ and close notepad++
in RSD Lite make sure you select the unzipped .XML
Click to expand...
Click to collapse
lol u are right it was win problem it work on my sis laptop win 7 XD finaly i got my phone back god bless u guys thx so much sd_shadow
and welder
last qustion did i have re root phone to install rom ?
Abdoobood said:
lol u are right it was win problem it work on my sis laptop win 7 XD finaly i got my phone back god bless u guys thx so much sd_shadow
and welder
last qustion did i have re root phone to install rom ?
Click to expand...
Click to collapse
yes need to re-root

Unstable phone

Hi,
My phone is currently unstable. It is rebooting pretty often with no obvious trigger. Also having reboots which return to the initial Google-setup. My settings.apk disappear yesterday, so I did another clean install. I'm on PAC-Rom at the moment, but was running Markox89's CM11 builds beforehand, and having issues there.
When wiping recently I've been doing a full system/data/cache wipe, as well as wiping cache/dalvik after installation. However I have not been formatting /sdcard/. Could this solve the issue?
Phone: i9300
ROM: PAC-i9300 Latest KK Nightly (20150128)
Kernel: Boeffla Kernel 2.7 NG CM11 Final
Modem: I9300XXUGND1
Bootl: I9300XXUGOA2
The following is a logcat which I started ~15 mins before a reboot occured.
Logcat (adb logcat *:E -v long > errors.log): http://pastebin.com/raw.php?i=1akST61A
PS: I have an exam tomorrow afternoon so I may not get around to too much testing in the next 24 hours.
Any help would be greatly received!
Thanks,
David
Try the freezing thread in general forum, test the memory for bad blocks.
Thanks for the reply,
I was following that process before a few months ago, and it might have improved the phone slightly so I'll keep on it for a bit.
My phone was most stable around a month ago where I had zero reboots in a week or two, but they started to appear again after a while.
It seems to be an error on a2dp, audio. Looks like driver loading failed but I'm no expert.
Sent from a stolen phone!
I've been playing around with a few more roms, both KK and LP but my phone is still getting reboots.
I'm now on PAC rom, the most recent KK nightly (from January '15)
I've started recording catlogs so I can now upload them here for every reboot in case there is something that can be helped.
Log from this morning, with filter set to errors: http://pastebin.com/raw.php?i=PpWqx6Xy
Thanks!
Flash back to stock and start again. If you need help let me know
When I flashed PAC ROM recently I did a full wipe including system and data and internal SD.
Wouldn't going back to stock have no effect?
Unless my modem and/or boot-loader may be causing issues?
Cheers
By going back to stock it resets all of your parameters and kernel, and boot files. This will resolve your issues if there is something wrong with the Bootloader also. I can help you if you need it
Also, I just noticed your running a lollipop Bootloader, with KitKat kernel and system. This could be an issue as well
KaosMaster said:
Also, I just noticed your running a lollipop Bootloader, with KitKat kernel and system. This could be an issue as well
Click to expand...
Click to collapse
Okay sounds like a good idea. I'm confident with adb and odin etc so shouldn't need any particular help.
I'm assuming this guide conforms to the standard approach: http://forum.xda-developers.com/galaxy-s3/general/fix-s3-to-factory-unroot-stock-recovery-t2323847
Cheers
Here are the complete ODIN Service files to restore your International GT-I9300 16GB device to I9300XXUGNJ2_I9300OXXGNJ1-OXX (Open) STOCK:<br />
<br />
CSC-OXX-I9300XXUGNJ2_I9300OXXGNJ1_2793257_REV00_user_low_ship.tar.md5<br />
<br />
https://drive.google.com/file/d/0B4RU_ZH5QUASenlHVlctVEZfUFE/view?usp=sharing<br />
<br />
This is ODIN v.3.10:<br />
https://drive.google.com/file/d/0B4RU_ZH5QUASSWhaMmdiaFJ1Tm8/view?usp=sharing<br />
<br />
This package is straight from Samsung and includes the PIT for partitioning!! <br />
<br />
These files are intended to be used with ODIN ONLY!! If at any time ODIN FAILS, pull battery, re-insert battery, go back to ODIN and try again.<br />
<br />
Download the two items, charge device to 100% battery, Download and install Device drivers from samsung if needed.<br />
<br />
www.samsung.com/support<br />
<br />
Unzip the CSC-i9300****.zip file.<br />
<br />
Unzip and Open "ODIN v.3.10.exe" as an "Administrator" on a Windows PC.<br />
<br />
Click on each of the 4 buttons below and browse to find matching file in extracted image folder:<br />
<br />
BL = BL-****.tar.md5<br />
AP = AP-****.tar.md5<br />
CP = MODEM-****.tar.md5<br />
CSC = CSC-****.tar.md5<br />
<br />
Check the following boxes:<br />
<br />
Auto-Reboot<br />
Re-Partition<br />
F. Reset Time<br />
NAND Erase All<br />
<br />
Put 100% charged device into ODIN Mode, and connect to PC USB with Original Cable.<br />
<br />
Check there two boxes in ODIN:<br />
<br />
Phone Bootloader Update<br />
Clear EFS Partition<br />
<br />
Hit the "Start" button<br />
<br />
Once the Device reboots, perform Two [2] FDR (Factory Data Reset).<br />
<br />
Phone is back to complete stock...

Categories

Resources