Develop Bugs

Help i bricked my f240k!! And my imei and model number is gone on the phone

1 ok using olleh f240k
2 flash singapore 988 rom on it
3 was ok but no network and some how my imei and model is not found in info
4 use lg support tool to do stock recovery
5 phone back to olleh stock firmware but still no network and got glish with some app
6 do 3 to 4 times of factory reset (still the same
7 try a couple of time flash stock olleh rom until the last try it stop half way and brick
8 now cant on my f240k but only can on to download mode only
9 still can be detected by pc and lg software soo try reinstall and recovery install hailf way 30% to 70% then it stop and say that lost connection on phone ect.....
Soo now my f240k lost its imei number and model number and only can on to download mode
pls helpppp
how do i recover my imei when i can get to the android os on my phone or is ther any onther way to fix this ???

boiflame said:
1 ok using olleh f240k
2 flash singapore 988 rom on it
3 was ok but no network and some how my imei and model is not found in info
4 use lg support tool to do stock recovery
5 phone back to olleh stock firmware but still no network and got glish with some app
6 do 3 to 4 times of factory reset (still the same
7 try a couple of time flash stock olleh rom until the last try it stop half way and brick
8 now cant on my f240k but only can on to download mode only
9 still can be detected by pc and lg software soo try reinstall and recovery install hailf way 30% to 70% then it stop and say that lost connection on phone ect.....
Soo now my f240k lost its imei number and model number and only can on to download mode
pls helpppp
how do i recover my imei when i can get to the android os on my phone or is ther any onther way to fix this ???
Click to expand...
Click to collapse
item 9 above, probably best is to try change your cable and reflash stock firmware.
NOTE: after you reflash and able to bootup the phone.... it probably will have 2 issue
1) imei not found and unable to connect to your mobile provider
2) your storage will show only 16GB
IMPORANT: did u do backup for the below block partition ? IF NOT, guess you can only use the phone as tablet.
adb.exe shell su -c "mkdir /sdcard/System/"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p12 of=/sdcard/System/12m9kefs1.img"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p13 of=/sdcard/System/13m9kefs2.img"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p15 of=/sdcard/System/15DRM.img"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p22 of=/sdcard/System/22eksst.img"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p21 of=/sdcard/System/21encrypt.img"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p26 of=/sdcard/System/26persist.img"

silentdrum said:
item 9 above, probably best is to try change your cable and reflash stock firmware.
NOTE: after you reflash and able to bootup the phone.... it probably will have 2 issue
1) imei not found and unable to connect to your mobile provider
2) your storage will show only 16GB
IMPORANT: did u do backup for the below block partition ? IF NOT, guess you can only use the phone as tablet.
adb.exe shell su -c "mkdir /sdcard/System/"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p12 of=/sdcard/System/12m9kefs1.img"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p13 of=/sdcard/System/13m9kefs2.img"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p15 of=/sdcard/System/15DRM.img"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p22 of=/sdcard/System/22eksst.img"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p21 of=/sdcard/System/21encrypt.img"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p26 of=/sdcard/System/26persist.img"
Click to expand...
Click to collapse
ok I got it working again soo I do not have a back up anyway to fix the network and imei?

There is an app for reinstating imei numbers in the gs3 forum but I don't know if it would work for you.
Sent from my LG-E980 using xda app-developers app

boiflame said:
ok I got it working again soo I do not have a back up anyway to fix the network and imei?
Click to expand...
Click to collapse
1) fast method
probably u can ask ppl with backup of the 240K to send u those backup files
NOTE: if restore from other ppl's backup file you will probably have the same IMEI as the person send u his backup files.
2) long tedios method
its kinda hard to explain here .. but involved using QPST, pull out or backup a .qcn file from your phone and manual edit the IMEI then push it back into your phone.
its a long shots.... but worth a try.
if your phone now still showing 16GB, u can have the 32gb back by formatting the partition.
adb shell
su
stop
/sbin/make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/userdata
reboot
NOTE: above command basically will
1) get adb shell
2) login root shell
3) stop/freeeze the system
4) formate the userdata using ext4 (note all of userdata will be gone)
5) reboot the phone
after reboot you should able to see back the 32gb storage.

merinko was
silentdrum said:
1) fast method
probably u can ask ppl with backup of the 240K to send u those backup files
NOTE: if restore from other ppl's backup file you will probably have the same IMEI as the person send u his backup files.
2) long tedios method
its kinda hard to explain here .. but involved using QPST, pull out or backup a .qcn file from your phone and manual edit the IMEI then push it back into your phone.
its a long shots.... but worth a try.
if your phone now still showing 16GB, u can have the 32gb back by formatting the partition.
adb shell
su
stop
/sbin/make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/userdata
reboot
NOTE: above command basically will
1) get adb shell
2) login root shell
3) stop/freeeze the system
4) formate the userdata using ext4 (note all of userdata will be gone)
5) reboot the phone
after reboot you should able to see back the 32gb storage.
Click to expand...
Click to collapse
my fone show 32 gb only network and imei

[GUIDE] Backing up a phone with broken display

I have seen several of threads asking about how to recover data from a phone that has a broken display.
Backing up a phone with broken display
Prerequisites
Rooted phone with broken display/digitizer/etc. Display is nonfunctional for whatever reason.
ADB for your platform. Downloads for Windows, Mac, and Linux can be found at my dev-host.
Drivers installed (Windows), rules file set up (Linux + Mac). Drivers for windows can be found here. Rules file for Linux can be found here.
Recovery file attached to this post. (twrp.img)
External sdcard with at least 2 GB free space inserted in your broken phone.
openrecoveryscript.txt file attached to this post.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Backing up your broken device
Extract the ADB zip somewhere convenient.
Move the twrp.img recovery file into the ADB extracted directory.
Move the openrecoveryscript.txt file into the ADB directory.
Open a command prompt / terminal window in the ADB directory.
Windows: Windows Key + R => Type in "cmd" then click "RUN".
Linux: Open a terminal window by selecting it from your applications.
ALL:
Code:
cd /path/to/ADB/directory
Pull the battery from your phone, place it back in and boot into recovery (VolUp + Home + Power).
Connect your phone to your computer
Make sure that the following command returns "XXXXXX recovery" before proceeding to the next step.
Code:
./adb devices
Expected output:
Code:
List of devices attached
XXXXXXX recovery
Now to install TWRP recovery to your device. Type the following commands ( after each line). Linux users: Make sure you prepend each command with "./", as in "./adb ...". ALL Make sure you type the commands in CAREFULLY.
Code:
adb push twrp.img /tmp/twrp.img
adb shell dd if=/tmp/twrp.img of=/dev/block/mmcblk0p18
Wait until the last command above returns an output similar to below before proceeding to the next step:
Code:
12916+0 records in
12916+0 records out
6612992 bytes (6.3MB) copied, 1.094278 seconds, 5.8MB/s
Now pull your phones battery and reboot into recovery once again.
Run the following command to make sure your phone has booted into recovery completely.
Code:
adb devices
Expected output
Code:
List of devices attached
XXXXXXX recovery
Type the following to set up a script that will backup your phone to your external sdcard.
Code:
adb push openrecoveryscript.txt /cache/recovery/openrecoveryscript
Reboot your phone once more. This time, TWRP will begin backing up your ROM.
Wait for the backup to finish. You will know it is finished when you feel your phone reboot once more.
Optionally, you can check the state of your backup by running the following command and reading the last couple lines of it's output.
Code:
adb shell cat /tmp/recovery.log
Click to expand...
Click to collapse
Click to expand...
Click to collapse
That's it! Your entire system (/system, /data, /cache, and boot) will be backed up to your external sdcard. Just pop the sdcard in your replacement phone and you're good to go.
Enjoy and donate to the TWRP devs! This would not be possible if TWRP did not use the OpenRecoveryScript scripting engine!

Hellua nice guide :thumbup:
TEAM MiK
MikROMs Since 3/13/11

Man Cnexus! You are everywhere! Lol.
Nice guide. This will save lots of people :thumbup:
------------------------
Sprint Galaxy S3 "Supernexus" Thanks To Cyanogenmod
Whiplashh Rom
Look it up.

Is this method specific to the S3? I have an old S2 that I need to recover some photos from.

Hmm...boot your S2 into recovery, then connect it to your computer, run the following command and post the output for me.
Code:
adb shell ls

Hopefully I never need this guide but I think it should be a sticky. Good job!

This seems very helpful thank you.
This is a good option as well
https://code.google.com/p/androidscreencast/

CNexus said:
I have seen several of threads asking about how to recover data from a phone that has a broken display.
Backing up a phone with broken display
Click to expand...
Click to collapse
Thanks so much for the how-to.
I have a rooted Sprint Galaxy S3 with a broken display. I'm having a problem with getting it into recovery mode.
I believe when I hold down VolUp+Home+Power and reboot, it's loading a menu that's prompting me to select one of the boot options. It otherwise just sits there and never actually boots.
I've tried to use adb to boot it into recovery mode, but it also just sits there until I press the home key, at which point it just boots into normal mode.
Is there a way I can bypass any menus or does anyone with a working system know which option I should select at the menu?
Thanks,
Alex

Is your display broken? What does "adb devices" show when you're in that mode?

[GUIDE] Authorize adb with broken digitizer.

So, yesterday my brothers Pit bull, Maggie, knocked my GS3 out of my hand and onto the cement driveway...
The result? A shattered screen, cracked display, and broken digitizer.
I wanted to perform a backup of my current rom (CM11 Latest Nightly) but figured out that my computer was not authorized for ADB.
Well, I wasn't about to let that stop me. Here is what I did to fix that little problem.
The following guide assumes that you already have the drivers for your phone installed and also that you have ADB set up.
I have only tested this on TWRP 2.7.1.0. I do not know if it will work on other recoveries.
First things first, power off your device by doing a battery pull.
This is the best way to ensure you are fully powered down since you can't see the screen.
Next, boot your device into recovery by pressing and holding the power, home, and volume up buttons.
Once you feel the device vibrate, release the buttons.
Plug in your phone and pull up a command prompt window.
Check and see if the device is being recognized by running
Code:
adb devices
.
Connect to the device by running
Code:
adb shell
.
Next, to mount the data partition where the files we need to edit are located, run the following code.
Code:
mount -t ext4 /dev/block/mmcblk0p15 /data
It is very important you type this exactly as written. Double check a few times to be sure.
Exit the shell by typing
Code:
exit
Now, we need to find our computer's adb key. For me, it was located in "C:\Users\%Username%\.Android\".
The file we are looking for is adbkey.pub.
Push this file to your device using
Code:
adb push adbkey.pub /sdcard/adbkey.pub
Pull up another shell by typing
Code:
adb shell
Remove the current adb key by typing
Code:
rm /data/misc/adb/adb_key
Insert the key into your phone's authorized keys by typing
Code:
cat /sdcard/adbkey.pub >> /data/misc/adb/adb_keys
Exit the shell
Reboot your device with
Code:
adb reboot
Profit! :good:

Hey buddy! Great tutorial! However, I'm getting an error trying to mount mmcblk0p15. I get the error:
"mount: mounting /dev/block/mmcblk0p15 on /data failed: Invalid argument"
Do i need super user privilege do to this?
Thanks! Great tutorial, btw.

[ROOT]How to Root KVT49L.D85110r and Install TWRP. My experience

I am not sure if this is the correct forum for this. Moderators, Please feel free to remove it or relocate it
First of all thanks to all amazing people on this forum ( thecubed,777jon,Dees_Troy, chainfire, supernoman, crashfocus, etc)
This is not my work . It is a compilation of what it worked for me from the work made by others. It is directly toward newbie users.
Instructions
1- Make sure you install LG G3 drivers in your computer( you can get them attached on this thread). Connect phone to the PC using USB cable. Make sure the phone is recognized when you plug it in with the usb cable
Also phone shall be connected as Media device (MTP), if it is in Charge Phone change it to MTP.
Scroll down this post. You will find the correct usb drivers attached. Install them in your pc.
2- Enable Developer options in your phone on Setting > General> About phone > Software information > and click seven times Build number until it enables it
3- Enable USB debugging on your LG G3 from your phones Settings > Developer options > tick ‘USB debugging’ check box. A window should pop up in your phone display to allow USB debugging. Select Allways Allow from This Computer and hit OK.
It will also be convenient to Enable installation of apps from Unknown Sources: Open phone’s Settings » select Security » Tick the “Unknown sources” check box (under Device administration section)
4- Download and unzip
- Pupledrake-Lite at http://downloads.codefi.re/thecubed/lg_g3/purpledrake/PurpleDrake-Lite_R03.tar.gz Thanks to Codefi.re
- Download and unzip the attached ADB LOCAL READY with TWRP recovery.img
Thanks to @Dees_Troy & TeamWin - for TWRP Touch recovery
ATTACHMENT IS HERE- JUST CLICK HERE
5- Download -Latest SuperSu at http://download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip Thanks to Chainfire
6- Transfer UPDATE-SuperSU-v2.40.zip to the internal sdcard
7- Open Purpledrake-Lite and Run purpledrake_windows.bat. It should detect your devices if it is not, you need to check if the drivers were installed properly and unplug-plug back your phone.
Hit Enter as instructed on the computer screen until it gains temporary root.
IMPORTANT : READ AND DO NOT CONTINUE TO PERMANENT ROOT INSTRUCTIONS DISPLAYED. FOLLOW INSTRUCTIONS TO CONTINUE WITH ADB INSTEAD.
Hit Ctrl+C to exit to use adb.
This process takes a few seconds and The phone start on download mode and it will stay on it.
8- Open ADB LOCAL READY folder you downloaded and hit Start Here.bat
Type "adb devices" to ensure that your phone is connected and it accept adb commands . On list of devices attached it should show LGD851........
Unplug it and plug it back if it is not .
NOTE: SOME PEEPS HAVE REPORTED PROBLEM WITH ADB NOT WORKING PROPERLY ON USB 3.0 PORTS. PLEASE USE USB 2.0 PORTS
9- Type "adb push recovery.img /temp"
You will see that it pushes the data. it should take a few seconds
Note: you may need to push it a few times if you do not find the recovery file on the /temp folder when you do step 12.
Some members stated that they need to push it ..5 times.
rubbamade tip
" This does work. If after you do the "adb push....", Hit the up key on your keyboard. What you just typed " adb push...." will appear again. Hit enter. It will "push" again. Hit up again. Hit enter. Do this at least 5 times. Now proceed with next step "adb shell"..... Should work now"
For some reason others user needed to push it more than 5 times, i assume that it is due to the file size of the image and your operating system and pc settings(i used win7). It is recommended to verify if it was pushed on step 12.
10- Type "adb shell" and it should go to shell command $
11- Then type "/temp/fakesu". This will put you in a superuser shell on your device. It should show su command line # .
12- Type "ls /temp" to make sure that recovery.img and fakesu are in /temp folder . If it is not, then you did not complete correctly the above instructions..repeat it
13- Type "dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery". it will take a few seconds to complete and install TWRP recovery.
14- Type type "reboot recovery" It should boot onto TWRP Touch recovery. it could take a few but it should
15- Once in TWRP, select install,go to the SD card directory, select UPDATE-SuperSU-v2.40.zip and install it. Reboot the phone once complete. Do not panic, it should take a while to cook and update applications, but it will, be patient.
16- Your device is rooted and with TWRP custom recovery. IF you do not see SuperSu in your application drawer, do not panic, just install it from the Play Store.
17- Now you are ready to install custom Roms, any application that requires root, or enjoy root features.
Quick References
How to Boot into TWRP(Recovery Mode)
1.Turn off your phone
2.Now, press and hold Power and Volume down buttons at the same time.
3.When the LG logo appears, release the keys.
4.Immediately press Power and Volume Down buttons again until the Hard Reset menu will be displayed.
5.Press volume down to Select "YES" on reset data. Do not panic, it will not . Select "yes" again . It will boot into TWRP recovery mode.
If you do not like hardware method you can use Quickboot or TWRP Manager applications from the Play store
How to Boot LG G3 Download Mode
-Disconnect your phone from PC.
-Power off your G3 and wait 4-5 seconds after lights go off.
-Hold the Volume Up button on phone, and while holding it, connect the phone to PC using a USB cable
If you get the "Windows cannot find '.\assets\windows\bin\mintty.exe'." error..on purpledrake temproot step 7.
Try just double-clicking on the .bat instead of running as admin.
Also make sure the script is extracted properly first before running
Disclaimer: It worked for me, but I am not responsible for any damages to your phone.

Your experience is very interesting vcurbel!
I was under the impression there was no way to root untouched stock 10R.
It would appear you have found a way! :good: Thanks for your contribution.
I am curious if anyone else has replicated this?

thank you so much had a little trouble but successfully rooted my device

Where was this guide yesterday?
Last week I just thought rooting build R was impossible as of yet, got fed up, and 5 minutes ago ran the LG Update tool to revert my phone back to stock/ Build C and root that way.

vcurbel said:
I am not sure if this is the correct forum for this. Moderators, Please feel free to remove it or relocate it
13- Type "dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery". it will take a few seconds to complete and install TWRP recovery.
Click to expand...
Click to collapse
dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
This command doesn't work for me. It shows, "cannot open for read: no such file or directory".
Can you help?
Edit: Nevermind, had to repush recovery. Didn't go through properly the first time. Thank you
Everything worked great. Thank you for the guide! Rooted on 10r!

NO GO
- Type "ls /temp" to make sure that recovery.img and fakesu are in /temp folder . If it is not, then you did not complete correctly the above instructions..repeat it
AT THIS POINT I AM GETTING "NOT FOUND". DID THE STEPS ABOVE SEVERAL TIMES.
I saw 8xxxkb data pushed after 'push'
==========================================================================================
C:\Users\nick\Downloads\ADB LOCAL READY>c:\windows\system32\cmd.exe
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\nick\Downloads\ADB LOCAL READY>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
LGD851xxxxxxxx recovery
C:\Users\nick\Downloads\ADB LOCAL READY>adb push recovery.img /temp
9716 KB/s (11245568 bytes in 1.130s)
C:\Users\nick\Downloads\ADB LOCAL READY>adb shell
[email protected]:/ $ /temp/fakesu
/temp/fakesu
# Is /temp
Is /temp
/temp/fakesu: Is: not found
#
=========================================================================================

sharkoparko said:
- Type "ls /temp" to make sure that recovery.img and fakesu are in /temp folder . If it is not, then you did not complete correctly the above instructions..repeat it
/temp/fakesu: Is: not found
#
=========================================================================================
Click to expand...
Click to collapse
try to redo step number 7. But, you are getting into su command line which is #
after you do the ls/temp on su #, you should get the list of files in your temp folder.....check if recovery and fakesu are there
then continue to step 13

vcurbel said:
try to redo step number 7. But, you are getting into su command line which is #
after you do the ls/temp on su #, you should get the list of files in your temp folder.....check if recovery and fakesu are there
then continue to step 13
Click to expand...
Click to collapse
Thanks. I did it several times, I did number 7 also. Phone is found, it says creating permaroot....Once I click CTRL C screen disappears then I go to ADB file and follow procedures. IT STILL DOES NOT WORK
===================================================================================
Welcome to PurpleDrake!
Please ensure your phone is connected, powered on, and USB debugging is properly enabled.
Your phone should be showing your homescreen with no other apps open. This is to ensure a clean state.
When you're ready, press [enter]...
Press [enter] to continue...
Waiting for device... Found device!
Your phone is a [ LG-D851 ] on [ TMO ] running SW version [ V10r ] ...
Alright. We're ready to go. We're going to temproot your phone first. Press enter when you're ready!
Press [enter] to continue...
Rebooting phone...
Waiting for device... .... Found device!
Found device, checking if vulnerable...
Yep, performing temproot...
Waiting for system to settle...
Temproot worked, all done here. Moving on...
Alright, now that you're temprooted, you can press CTRL-C here and get
a temproot prompt through 'adb shell /temp/fakesu' if you're so inclined...
However, if you'd like to permaroot, let's continue.
Press [enter] to continue...
===============================================================================================
DO I NEED TO RE-ROOT?

sharkoparko said:
Thanks. I did it several times, I did number 7 also. Phone is found, it says creating permaroot....
DO I NEED TO RE-ROOT?
Click to expand...
Click to collapse
Here is the problem. You pressed to continue (enter) to create permanent root after temporary root was created
You need to press CTRL C instead , then it will exit......then continue to next step with ADB LOCAL READY.
Ill clarify this better on step 7.
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app

vcurbel said:
Here is the problem. You pressed to continue (enter) to create permanent root after temporary root was created
You need to press CTRL C instead , then it will exit......then continue to next step with ADB LOCAL READY.
Ill clarify this better on step 7.
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
Click to expand...
Click to collapse
Once I click CTRL C screen disappears then I go to ADB file and follow procedures. IT STILL DOES NOT WORK
That's what I do. I clicked enter first time rooting following purple instructions. Then I realized it does not work with January update. I run purple drake again (after I found this "fix") and, as I said, I DO NOT PROCEED WITH ENTER. I use CTRL C. The window closes and I open ADB, then click start hereand follow the rest of the procedures. So YES I did click enter once initially (because purple drake post is not updated that it does not work with JAN 15 update).

sharkoparko said:
Once I click CTRL C screen disappears then I go to ADB file and follow procedures. IT STILL DOES NOT WORK
That's what I do. I clicked enter first time rooting following purple instructions. Then I realized it does not work with January update. I run purple drake again (after I found this "fix") and, as I said, I DO NOT PROCEED WITH ENTER. I use CTRL C. The window closes and I open ADB, then click start hereand follow the rest of the procedures. So YES I did click enter once initially (because purple drake post is not updated that it does not work with JAN 15 update).
Click to expand...
Click to collapse
Ok....lets do it one at a time
Once you open and run ADB LOCAL READY. When you type adb devices, is it show your device?
Let me know on which step you got stuck.
Ill try to help you
Sent from my LG-D851 using XDA Free mobile app

Just got home with a Craigslist buy.
rooted in 15min thanks vcurbel !
now to find CM12 for this baby

hi sorry for the newbiness but for some reason i donload everything i need, basically preperation is done to the T, but as soon as i click on purpledrake_windows.bat it goes into dos window and complety exits out in less then a second, so fast that i can barely read whats on that lil black screen, im pretty sure i can make out "command not found" at the end of it..any help would be greatly appreciated

tomez206 said:
hi sorry for the newbiness but for some reason i donload everything i need, basically preperation is done to the T, but as soon as i click on purpledrake_windows.bat it goes into dos window and complety exits out in less then a second, so fast that i can barely read whats on that lil black screen, im pretty sure i can make out "command not found" at the end of it..any help would be greatly appreciated
Click to expand...
Click to collapse
Did you run it as Administrator?
Did you install LG drivers and the device is being recognized as Media device?
Sent from my LG-D851 using XDA Free mobile app

all drivers are installed, the device is recognized, and nothing, when i do run it as administrater i get a whole different error msg
vcurbel said:
Did you run it as Administrator?
Did you install LG drivers and the device is being recognized as Media device?
Sent from my LG-D851 using XDA Free mobile app
Click to expand...
Click to collapse
---------- Post added at 08:43 AM ---------- Previous post was at 08:38 AM ----------
windows cannot find '.\assets\windows\bin\mintty.exe'. Make sure you type the name correctly and try again...thats the error i get when trying to run as administrator

tomez206 said:
all drivers are installed, the device is recognized, and nothing, when i do run it as administrater i get a whole different error msg
---------- Post added at 08:43 AM ---------- Previous post was at 08:38 AM ----------
windows cannot find '.\assets\windows\bin\mintty.exe'. Make sure you type the name correctly and try again...thats the error i get when trying to run as administrator
Click to expand...
Click to collapse
It seems your windows os is missing the default mintty.exe terminal...
Google it and you will find a solution to manually install it.
Or use other pc
Sent from my LG-D851 using XDA Free mobile app

tomez206 said:
hi sorry for the newbiness but for some reason i donload everything i need, basically preperation is done to the T, but as soon as i click on purpledrake_windows.bat it goes into dos window and complety exits out in less then a second, so fast that i can barely read whats on that lil black screen, im pretty sure i can make out "command not found" at the end of it..any help would be greatly appreciated
Click to expand...
Click to collapse
If I recall if the PD batch file/script is closing on you or giving you trouble, then you can run the script manually.
See link below to thecubed PD lite thread and read the 5th grey portion down of the OP, it is titled:
"But, what if I don't want to run your script to root?"
If you must use command line because the PD batch file/script is closing immediately just be sure to STOP after gaining temporary root!
From OP step 7:
IMPORTANT : READ AND DO NOT CONTINUE TO PERMANENT ROOT INSTRUCTIONS DISPLAYED. FOLLOW INSTRUCTIONS TO CONTINUE WITH ADB INSTEAD. [/FONT]

lagvoid said:
dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
This command doesn't work for me. It shows, "cannot open for read: no such file or directory".
Can you help?
Edit: Nevermind, had to repush recovery. Didn't go through properly the first time. Thank you
Everything worked great. Thank you for the guide! Rooted on 10r!
Click to expand...
Click to collapse
Hello,
I am also having the same issue. I tried the above steps a couple times and am not sure if I am doing something wrong (more than likely I am). What did you mean by repush recovery?

Try step 9 again
9- Type "adb push recovery.img /temp"
You will see that it pushes the data. it should take a few seconds

vcurbel said:
Ok....lets do it one at a time
Once you open and run ADB LOCAL READY. When you type adb devices, is it show your device?
Let me know on which step you got stuck.
Ill try to help you
Sent from my LG-D851 using XDA Free mobile app
Click to expand...
Click to collapse
-------------------------------------------------------------------------------------------------------------------------------------
C:\Users\nick\Downloads\ADB LOCAL READY>c:\windows\system32\cmd.exe
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\nick\Downloads\ADB LOCAL READY>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
LGD851xxxxxxxx recovery
C:\Users\nick\Downloads\ADB LOCAL READY>adb push recovery.img /temp
9682 KB/s (11245568 bytes in 1.134s)
C:\Users\nick\Downloads\ADB LOCAL READY>adb shell
[email protected]:/ $ /temp/fakesu
/temp/fakesu
# Is /temp
Is /temp
/temp/fakesu: Is: not found
# dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
/temp/recovery.img: cannot open for read: No such file or directory
#
--------------------------------------------------------------------------------
Yes, The phone is recognized and the file as you see was pushed (see script above). I think there is some issue with this method, as other people are reporting problems following the procedure in post #1??!! I guess it work for some and it does not for others.

Need help, Note 4 SM-N910A

ok here we go, i have a Note 4 sm-n910a and i update to 5.1.1 but when its finish send me a message: "Android is starting... optimizing app 1 of 23" and on 12 of 23 boop, and restart again and again. I try put AP file in ap slot, BL on BL slot, cp on cp and CSC on csc, and finish ok, but when restart do that again and again, even i try puting the pit file but the same, i don´t no what happen (i can´t do downgrade)
There is a solution , or blockage stayed forever? :crying:

One time when I was messing with a hidden menu this happened to me. Phone would only boot loop to the exact spot you're saying. I replied to you in the other thread. If what I said doesn't work you will have to take it in for warranty. I had to take mine in for warranty because of messing with the wrong options in the hidden menu. ATT tried everything including reflashing with their utility and it couldn't fix the issue. So, they gave me a new phone right there. I don't know where you are but if you go to the nearest ATT store they should give the steps on how to get it replaced. Hopefully you have a ATT service center near you so you can just get it replace then and there. Btw, don't mention anything about flashing with Odin. I don't think it violates the warranty since you didn't use custom firmware you just used the official firmware and used Odin which is Samsung software. However don't mention ever using Odin, just say that you had tried upgrading your phone and after the upgrade this happened.

tonys.94 said:
One time when I was messing with a hidden menu this happened to me. Phone would only boot loop to the exact spot you're saying. I replied to you in the other thread. If what I said doesn't work you will have to take it in for warranty. I had to take mine in for warranty because of messing with the wrong options in the hidden menu. ATT tried everything including reflashing with their utility and it couldn't fix the issue. So, they gave me a new phone right there. I don't know where you are but if you go to the nearest ATT store they should give the steps on how to get it replaced. Hopefully you have a ATT service center near you so you can just get it replace then and there. Btw, don't mention anything about flashing with Odin. I don't think it violates the warranty since you didn't use custom firmware you just used the official firmware and used Odin which is Samsung software. However don't mention ever using Odin, just say that you had tried upgrading your phone and after the upgrade this happened.
Click to expand...
Click to collapse
but if I buy used for ebay, i don have a contract with att, can i change the phone?, its never fixed and on knox 0x0

Sent from my SAMSUNG-SM-N915A using XDA Free mobile app
Talking [GUIDE] Fix N910A Boot Loop - Unknown Baseband (step by step)
Hello friends
I have a few people asking questions on solution for N910 boot-loop, I want to make step-by-step guide to answer all questions.
Problem caused by changing *#9090# and possibly downgrade as well.
Takes time, several tries, don't worry.
I had the same problems and this method solved it.
1. Downgrade to 4.4.4 via Odin. Extract OC4, extract Odin, open Odin, select four files into correct position (BL, AP, CP, CSC) 4.4.4 OC4 Odin 3.09 (Samsung Mobile drivers required)
2. Once on 4.4.4 or below, enable developer options by tapping "build version" several times, enable USB debugging & mock location, and install KingRoot 4.0.0.233 to phone. Caution, newer versions did not work for me.
3. Open "Command Prompt" and type "adb version" should reply with "Android Debug Bridge version x.x.x", if does not, change to the correct directory where adb is installed via "cd" command. Need ADB? Here
4. These next two steps can be a little tricky as the phone often reboots before completed, must work quickly, I suggest copying the long command, then paste when ready.
5. Connect to working WiFi. Turn off your phone, reboot, or wait for it to reboot itself. Soon as phone turns on, open KingRoot, soon as WiFi connected notification appears, touch button in center of KingRoot app, soon as KingRoot reaches 30%, began adb commands.
6. ADB commands: first command "adb shell", second command "su", third command "dd if=/dev/zero of=/dev/block/mmcblk0p10 | dd if=/dev/zero of=/dev/block/mmcblk0p13 | dd if=/dev/zero of=/dev/block/mmcblk0p14 | dd if=/dev/zero of=/dev/block/mmcblk0p15 | dd if=/dev/zero of=/dev/block/mmcblk0p16" phone will reboot or you can reboot and after reboot boot-loop and unknown baseband will be fixed! Can now write new IMEI via "Write Cert" and possibly "Write QCN" if any network troubles, then all good to go!
7. Any questions feel free to contact me on skype: brandon.sisco or phone: 949.482.7058 I'm happy to walk you through any steps.
Once you see results, I have worked hard on this complete solution for many weeks, I would appreciate any donation. Secure paypal donate here
Thank you ecs87 for the help with adb wipe efs commands
---------- Post added at 08:28 AM ---------- Previous post was at 08:26 AM ----------
Sent from my SAMSUNG-SM-N915A using XDA Free mobile app
This is the Web address I used
http://forum.gsmhosting.com/vbb/f684/guide-fix-n910a-boot-loop-unknown-baseband-step-step-1961415/

lamarwallace said:
Sent from my SAMSUNG-SM-N915A using XDA Free mobile app
Talking [GUIDE] Fix N910A Boot Loop - Unknown Baseband (step by step)
Hello friends
I have a few people asking questions on solution for N910 boot-loop, I want to make step-by-step guide to answer all questions.
Problem caused by changing *#9090# and possibly downgrade as well.
Takes time, several tries, don't worry.
I had the same problems and this method solved it.
1. Downgrade to 4.4.4 via Odin. Extract OC4, extract Odin, open Odin, select four files into correct position (BL, AP, CP, CSC) 4.4.4 OC4 Odin 3.09 (Samsung Mobile drivers required)
2. Once on 4.4.4 or below, enable developer options by tapping "build version" several times, enable USB debugging & mock location, and install KingRoot 4.0.0.233 to phone. Caution, newer versions did not work for me.
3. Open "Command Prompt" and type "adb version" should reply with "Android Debug Bridge version x.x.x", if does not, change to the correct directory where adb is installed via "cd" command. Need ADB? Here
4. These next two steps can be a little tricky as the phone often reboots before completed, must work quickly, I suggest copying the long command, then paste when ready.
5. Connect to working WiFi. Turn off your phone, reboot, or wait for it to reboot itself. Soon as phone turns on, open KingRoot, soon as WiFi connected notification appears, touch button in center of KingRoot app, soon as KingRoot reaches 30%, began adb commands.
6. ADB commands: first command "adb shell", second command "su", third command "dd if=/dev/zero of=/dev/block/mmcblk0p10 | dd if=/dev/zero of=/dev/block/mmcblk0p13 | dd if=/dev/zero of=/dev/block/mmcblk0p14 | dd if=/dev/zero of=/dev/block/mmcblk0p15 | dd if=/dev/zero of=/dev/block/mmcblk0p16" phone will reboot or you can reboot and after reboot boot-loop and unknown baseband will be fixed! Can now write new IMEI via "Write Cert" and possibly "Write QCN" if any network troubles, then all good to go!
7. Any questions feel free to contact me on skype: brandon.sisco or phone: 949.482.7058 I'm happy to walk you through any steps.
Once you see results, I have worked hard on this complete solution for many weeks, I would appreciate any donation. Secure paypal donate here
Thank you ecs87 for the help with adb wipe efs commands
---------- Post added at 08:28 AM ---------- Previous post was at 08:26 AM ----------
Sent from my SAMSUNG-SM-N915A using XDA Free mobile app
This is the Web address I used
http://forum.gsmhosting.com/vbb/f684/guide-fix-n910a-boot-loop-unknown-baseband-step-step-1961415/
Click to expand...
Click to collapse
Thank´s man, but when you are on 5.1.1, can´t do a downgrade, i have my phone brick, i´m fu.... :crying:

lamarwallace said:
Sent from my SAMSUNG-SM-N915A using XDA Free mobile app
Talking [GUIDE] Fix N910A Boot Loop - Unknown Baseband (step by step)
Hello friends
I have a few people asking questions on solution for N910 boot-loop, I want to make step-by-step guide to answer all questions.
Problem caused by changing *#9090# and possibly downgrade as well.
Takes time, several tries, don't worry.
I had the same problems and this method solved it.
1. Downgrade to 4.4.4 via Odin. Extract OC4, extract Odin, open Odin, select four files into correct position (BL, AP, CP, CSC) 4.4.4 OC4 Odin 3.09 (Samsung Mobile drivers required)
2. Once on 4.4.4 or below, enable developer options by tapping "build version" several times, enable USB debugging & mock location, and install KingRoot 4.0.0.233 to phone. Caution, newer versions did not work for me.
3. Open "Command Prompt" and type "adb version" should reply with "Android Debug Bridge version x.x.x", if does not, change to the correct directory where adb is installed via "cd" command. Need ADB? Here
4. These next two steps can be a little tricky as the phone often reboots before completed, must work quickly, I suggest copying the long command, then paste when ready.
5. Connect to working WiFi. Turn off your phone, reboot, or wait for it to reboot itself. Soon as phone turns on, open KingRoot, soon as WiFi connected notification appears, touch button in center of KingRoot app, soon as KingRoot reaches 30%, began adb commands.
6. ADB commands: first command "adb shell", second command "su", third command "dd if=/dev/zero of=/dev/block/mmcblk0p10 | dd if=/dev/zero of=/dev/block/mmcblk0p13 | dd if=/dev/zero of=/dev/block/mmcblk0p14 | dd if=/dev/zero of=/dev/block/mmcblk0p15 | dd if=/dev/zero of=/dev/block/mmcblk0p16" phone will reboot or you can reboot and after reboot boot-loop and unknown baseband will be fixed! Can now write new IMEI via "Write Cert" and possibly "Write QCN" if any network troubles, then all good to go!
7. Any questions feel free to contact me on skype: brandon.sisco or phone: 949.482.7058 I'm happy to walk you through any steps.
Once you see results, I have worked hard on this complete solution for many weeks, I would appreciate any donation. Secure paypal donate here
Thank you ecs87 for the help with adb wipe efs commands
---------- Post added at 08:28 AM ---------- Previous post was at 08:26 AM ----------
Sent from my SAMSUNG-SM-N915A using XDA Free mobile app
This is the Web address I used
http://forum.gsmhosting.com/vbb/f684/guide-fix-n910a-boot-loop-unknown-baseband-step-step-1961415/
Click to expand...
Click to collapse
Thank u. it work like charm. Many thank to your help.