Database Info

[Q] SBF Flash Error - FEBE 0047

So I have read thoroughly and have exhausted every solution I can find, to no avail. That said, here is what I'm dealing with:
I am trying to flash my D2G with the .330 SBF file.
Just so there is no confusion. I am using full admin rights: I got to rsd.exe in the folder, shift-rgt click, etc.
For full discloser, on the bootloader screen (up arrow + power) it says:
Bootloader
D2.35
Battery OK
OK to Program
Connect to USB
Data Cable
Upon flashing I get this error:
ERROR: Phone[0000]: Error sending JUMP command Device API Error: 0xE0020047 Address: 0x82000000 Command: JUMP - on device ID 0.
I have tried putting the sbf file in every suggested folder (my docs, root, root/moto, etc) Nothing works.
My USB is 2.0 so that isn't the issue.
Can anyone help break through this wall? I have been reading and trying for hours. I wouldn't post here unless it was an absolute last resort. Thank you in advance for helping.

strakajagr said:
So I have read thoroughly and have exhausted every solution I can find, to no avail. That said, here is what I'm dealing with:
I am trying to flash my D2G with the .330 SBF file.
Just so there is no confusion. I am using full admin rights: I got to rsd.exe in the folder, shift-rgt click, etc.
For full discloser, on the bootloader screen (up arrow + power) it says:
Bootloader
D2.35
Battery OK
OK to Program
Connect to USB
Data Cable
Upon flashing I get this error:
ERROR: Phone[0000]: Error sending JUMP command Device API Error: 0xE0020047 Address: 0x82000000 Command: JUMP - on device ID 0.
I have tried putting the sbf file in every suggested folder (my docs, root, root/moto, etc) Nothing works.
My USB is 2.0 so that isn't the issue.
Can anyone help break through this wall? I have been reading and trying for hours. I wouldn't post here unless it was an absolute last resort. Thank you in advance for helping.
Click to expand...
Click to collapse
Confirm that your SBF file is not corrupt. Try downloading it from a different source and check hashes

I have tried 3 sbf's thus far. 2 .330's (from different locations) and 1 .290. The error message is always the same. I'm not sure if it matters, but I have clockword mod installed on my phone as well as Fission.

I'm not sure if having Mods and roms who affect your phone. But just incase have you tried clearing the cache,data,partition from the recovery menu?

I have... again, no luck. It just appears that rsd lite flat out can't communicate with my phone even though it definitely SEES the phone when it's connected. For the life of me I can't figure out why. I found ONE thread on another site where someone posted the same error and reported the same problem. Someone linked him to a boiler plate SBF installation instruction page, which obviously I have tried unsuccessfully several times. It's killing me knowing that there is so much more performance in my phone that I just can't get. My original Droid outperformed this POS. UGH

That certainly is frustrating. The only thing I can think of is trying a different USB cable that is shielded or otherwise, or another computer/OS maybe it's causing a error. If you've already tried that with no results, all I can say is sorry man and keep trying.

I was just reading this thread: http://forum.xda-developers.com/showthread.php?t=1236781 where the final poster said there are a couple of bad .330 sbfs circulating the web, and that the best way around it was to try to sbf a .29 and then ipdate from there.
BTW, op, I agree. My droid one can kick my D2G's ass blindfolded.
Good luck,
Dan

Hi mate, i have had this issue before, please try this as this is the way around my issue =
follow this link and download the rar file (http://www.multiupload.com/FIW8B8TJ7I), flash this file (using rdslite 4.9 , Make sure it is rds lite 4.9!) = http://www.mediafire.com/file/9c6u55c26e1h9y1/RSD Lite 4.9.rar
Being on clock work etc... wont make a differnce but to put your phone in boot loader mode, please do it this way and not the other loaders way.
turn off the phone, press and hold the up and down volume buttons together (make sure you are pressing and holding them down together keep them hold down and dont let go) press the power button while still holding the volume buttons and wait till bootloader comes and then let go, onces it says it in there
Launch RSDLite (make sure device appears in window)
Select SBF (doesnt matter where the file is, just point it to the right place)
click start.
Once it gets to 100% , pull it out and restart the phone (it should reboot it normally but I find it doesn't always do it) so either unplug and let it reboot or pull the battery out and reboot, fingers crossed it will boot in to stock and then you can upgrade from there.

"No such file or directory" help!
Hello,
I am having issues following these instructions as a part of the instructions from
droidforums' root-droid-1-regardless-os-version
after running this:
chmod +x sbf_flash
Then running
sudo ./sbf_flash update.zip
I get the following:
[email protected] ~ $ sudo ./sbf_flash update.zip
[sudo] password for gjohnhazel:
SBF FLASH 1.24 (mbm)
opticaldelusion
update.zip: No such file or directory
Usage: sbf_flash <filename>
My Droid is plugged in, with update.zip in the root of the SD Card and Bootloader 2C.7C with Transfer Mode set to USB.
Can anyone help?
Note: Where it says "opticaldelusion" it's actually the link, but I'm not allowed to have hyperlinks in this message.

sbf_flash is used to load an SBF image (which should be stored on your PC for sbf_flash to access it) into your phone.
It's not a tool to flash OTA/normal update packages.
To flash a normal update.zip you need to use either stock (for stock firmware updates) or ClockworkMod Recovery (for custom ROMs).

[Q] Hard bricked kindle fire 2(omap4430)

First of all this is my first post and I am a complete NOOB.
Also I apologize in advance if I break any rules with this post and please excuse my terrible grammar and spelling.
Computer 1:Windows 7 Ultimate 32bit
Computer 2:Ubuntu 12.04 LTS
Device: Amazon Kindle Fire 2nd Gen
I will try to provide as much information as I can stating how I got here
Eastern Time:
11:00pm : Decided to root and flash a custom rom on my friends kindle fire hd 10.4.6 have rooted and flashed my first gen kindle and a galaxy s before successfully. So i looked around the forums and found this http://forum.xda-developers.com/showthread.php?t=2494232 The last comment lead me to this site staticchaos.freeoda.com/fire/ where I downloaded the following files
1)Kindle Fire USB driver
2) RootFire.zip
The RootFire.zip had http://imgur.com/uqFGWyu
and i rooted the device using the RunME shown http://imgur.com/OCYoM9p
11:49pm: Happy and dandy rooted and superuser was installed no problem now I had to install TWRP so I followed http://forum.xda-developers.com/showthread.php?t=2404120 and
I thought everything was fine until I realized that in the post the version he says to download is CM-10.1 and I had downloaded cm-11-20140106-NIGHTLY-otter2.zip from the link he provided. I realized that after I was in TWRP after wiping all the caches and the system I went to install it and it gave me an error which i don't remember what it said.
12:40am: So now im trying to figure how the hell to mount the kindle back so I can transfer the rom out and put the correct one in. I see there is a mount option in TWRP but it would always show up as a hidden removeable disk and when i looked at the command line it said
"E: unable to locate volume information for usb storage mode"
So i googled that and found this post http://forum.xda-developers.com/showthread.php?t=2274315
I figured okay I don't have a fastboot cable so let me try the sideboot loader. But now my computer running windows 7 ultimate 32 bit was not recognizing the kindle like before. It came up as kindle fire2 and the previous drivers werent working
so when i ran cmd an issued the adb devices command nothing showed and I was unable to sideload anything.
So then i got to thinking the error said it could not locate volume information, there was an option in TWRP that said format or partition I don't remember so the idea in my noob brain was ill partition a small part of the memory inside to hold the correct ROM and than flash it using TWRP and problem solved. until this point I could turn my kindle off and on and be able to get into TWRP no problem just hitting the power button.
After the third try of partitioning and each time failing because it could not mount "/data"
i got fustrated and went looking for answers but the kindle was dying at 3% so i shut it off and let it charge while i looked. MISTAKE
i powered it off via the power button and the light disappeared when I went to turn it on again I had no luck BLACK SCREEN and nothing
SO i turned on my xbox and decided Ill play while it charges.
1:40am: no luck nothing on the screen cant get it to come up on the computer F Me i bricked this thing. Finally wiggle the usb around plug out of the hub and directly into the computer and BAM OMAP4430 is being connected and disconnected continuously
YES WE HAVE LIFE. So i began looking at what it is and found several post
http://forum.xda-developers.com/showthread.php?t=1413951
http://forum.xda-developers.com/showthread.php?p=20565446
http://forum.xda-developers.com/showpost.php?p=19800610&postcount=74
First i found out that im in the "cpu's USB boot mode. You need to send the cpu something to boot over usb or it will loop forever trying to find something to boot off flash".
so I powered up my vmware and transfered all the files in I would need to run 2) Open a terminal and sudo or su to root. It's easier that way.
3) Unplug the USB or AC adapter if it's plugged into the KF. But have the USB cable's A end plugged into the PC. This is very important.
4) Turn the power completely off. Do a shutdown if actually running Android, or hold the power button until there's no LED or backlight.
5) Pry open the back cover. The iFixit teardown (Google it) gives some ideas on how to do it, but be really careful because it's easy to snap the tabs along the long sides. DID NOT DO THIS SINCE I HAD READ ELSEWHERE I WAS ALREADY IN THIS MODE
6) The power must still be off. If you accidentally powered it back on, turn it back off.
7) Run:
Code:
./usbboot aboot.bin u-boot.bin; ./fastboot boot twrp-blaze-2.0.0RC0.img
This will chain load aboot, FIREFIREFIRE, then TWRP.
This got me nothing expect waiting for
OMAP44xx device...
sending 2ndstage to target...
waiting for 2ndstage response...
unexpected 2ndstage response
< waiting for device >
and then the terminal just stood there so then on another thread I read
http://forum.xda-developers.com/showthread.php?t=1413358
" run the script usb_fix_parts_and_install_fff_twrp and plug your device in while off when it says <waiting for omap44xx device> in the terminal. The script should run when your device boots up because it`s in this state. I don`t believe you will even need the short trick"
yes a solution finally after looking for so long!
3:37am: download the files run the script run the
[email protected]:/home/orlando/Desktop/rekindle/rekindle# ./fk
5837+1 records in
5837+1 records out
5977554 bytes (6.0 MB) copied, 4.69615 s, 1.3 MB/s
Stopping any running adb servers...
Done. Tools are in /root/firekit. Files copied to USB are likely in /cdrom
Scripts:
install_fff_twrp_from_stock - install FFF and TWRP while in stock Android
install_fff_twrp - install FFF and TWRP while in fastboot
fix_parts - restore partition table to stock while in fastboot
normal_boot - set the bootmode to boot android and reboot while in fastboot
usb_boot_twrp - USB boot TWRP without installing
usb_install_fff_twrp - USB boot FFF, install FFF and TWRP
usb_fix_parts_and_install_fff_twrp - USB boot FFF, restore partition
table to stock, install FFF and TWRP
Good luck. -pokey9000
[email protected]:~/firekit#
[email protected]:~/firekit#
[email protected]:~/firekit#
[email protected]:~/firekit# usb_fix_parts_and_install_fff_twrp
Loading FFF through USB...
?
waiting for OMAP44xx device...
sending 2ndstage to target...
waiting for 2ndstage response...
unexpected 2ndstage response
Fixing partitions...
< waiting for device >
"YES ITS GONNA FIX IT"
20 mins later
"NOPE"
It froze there and the kindle kept connecting and disconnecting it is now 4:30am
it will still only connect and disconnect as OMAP4430
If the developers or someone who knows more than me would be kind enough to lead me in the right direction I would appreciate it
I have tried hard to fix this thing and no luck.

+1
+1

Is this considered as terminal?
As a super hard core bricked?
*i'm here now all ill be doing now buying is broken Screen Kindle and assemble with my good screen

Try search on YouTube for Tekify lollipop or marshmallow on Kindle fire HD. He has a real easy to follow step by step. I used him on 2 kindles both with success in minutes.
Or: www.tekify.co.uk/kindle-fire-hd/roms/cyanogenmod-13-6-0-marshmallow

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

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

FYI installing TWRP will offer to automatically root the device for you when you reboot back into Android.
Also, CWM for our devices is horribly outdated, and last I checked completely unable to flash any KK-based ROM. I wouldn't recommend it - OpenRecovery or TWRP are my recommendations.

arrrghhh said:
FYI installing TWRP will offer to automatically root the device for you when you reboot back into Android.
Also, CWM for our devices is horribly outdated, and last I checked completely unable to flash any KK-based ROM. I wouldn't recommend it - OpenRecovery or TWRP are my recommendations.
Click to expand...
Click to collapse
The two months I had my Photon Q working CWM worked great for me. Did a few backups and didn't have to re-root after each boot. But it always helps to have more options so thanks for mentioning both alternatives!

protivakid said:
The two months I had my Photon Q working CWM worked great for me. Did a few backups and didn't have to re-root after each boot. But it always helps to have more options so thanks for mentioning both alternatives!
Click to expand...
Click to collapse
I'm pretty sure CWM won't flash KK-based ROM's as I stated previously.
Also, you shouldn't have to re-root - TWRP just does the rooting for your if you are installing a custom recovery for the first time so you don't have to do it manually .

arrrghhh said:
I'm pretty sure CWM won't flash KK-based ROM's as I stated previously.
Also, you shouldn't have to re-root - TWRP just does the rooting for your if you are installing a custom recovery for the first time so you don't have to do it manually .
Click to expand...
Click to collapse
Thanks again! I just used the stock rom but rooted during my brief time with the phone but this will help those who wish to use KK on the Photon.

RISING THIS TREAD FROM THE DEAD!!!
WHO STILL HAS THIS PHONE WORKING??
i blue screened my LG G3 so i pulled this phone off my dash in the bimmer to possibly try to root but it runs so damn slow now. any support will be much appreciated this is by far the most reliable device i ever purchased (400 bucks out the door brand new fml)
i will try to root later this week but big shout out to XDA for all thier threads on android ive been rooting since the
optimus line
cheers!

[Q] Accept RSA key for ADB with a broken screen - any ideas?

Hi All,
My GS3 has a broken screen, which displays nothing and accepts no touch input. It has an unlocked bootloader, rooted, and is running some version of CWR and a recent CM11 snapshot. The phone boots fine, is on my wifi, receives notifications, can accept Play Store app installs, etc. I figured, if I could connect over ADB, I could do a lot of neat things with the device (without replacing the screen). USB debugging is enabled, but the kicker is, I didn't "remember" my computer's RSA key, so I can't connect over ADB. I need to somehow bypass this.
Things I've thought of:
- If I could input a touch event/click, I could blindly click and hope I accepted the RSA key. With a mouse connected over USB OTG I could click, but the prompt disappears if the computer's USB cable is unplugged. I have a bluetooth mouse, but I've reflashed since the last time I paired it.
- I might be able to manually add the RSA key, by copying it from my computer and adding the line to /data/misc/adb/adb_keys. But then somehow I need to be able to write to /data. I think I might I be able to do that by booting into recovery and using adb to pull the file and push a modified one, but when I try (pull battery, hold volume up, home, power for several seconds) and connect it to my PC, nothing shows up when I run "adb devices".
- I've heard of flashing an "insecure boot image" that wouldn't ask for the RSA prompt. I wouldn't know where to start with that one and would need some hand-holding to get that done.
Does anyone have a suggestion?

Hi,
Try the second method, it should work.
i pulled the adb_keys from another phone that worked, same model.
then reboot into recovery twrp on the phone with broken screen and adb push the file to the location, reboot it and it worked.

Although this thread is really old, I came across the same problem. I used teamv*er to remote control my phone from the computer. My touch screen was non-responsive, but my lcd was still working...

I am in this same situation...
Verizon Note 3
Rooted
SafeStrap
Custom Rom (Jasmine I think)
A few days ago I broke my LCD (while in an otterbox and isn't the first time... GRRRRR.) So now I want to pull files and such from the phone using ADB or use the phone via USB with androidscreencast.jnlp (java applet) but I must have never accepted my RSA fingerprint prior to breaking the screen...
Anyone had any success bypassing the fingerprint or found another method to edit /data/misc/adb/adb_keys?
I can see the phonje via ADB...
[email protected]:~# adb devices
List of devices attached
63db4a57 unauthorized
...but with it being unauthorized I can't read/write...
Any suggestions? Thanks in advance.

Question Trouble rooting my Pixel 7 Pro

I am trying to root my new Pixel 7 Pro, build number TD1A.220804.031, but have run into an issue. Let me explain what I have done and where the issue arose:
I am following the instructions here: https://www.xda-developers.com/how-to-unlock-bootloader-root-magisk-google-pixel-7-pro/. I found the factory image for my phone, downloaded it, then downloaded/installed the Payload Dumper Tool, extracted init_boot.img, copied it to my phone, patched it using Magisk, and copied it back to my computer. Took a bit longer than expected, but no problems.
Via the phone’s setting, I enabled OEM Developer options and then allowed OEM Unlocking. Again, no issues. I then turned the phone off, attached the phone to my computer using a USB cable, and then booted it so that the bootloader menu was visible. In a command window on my PC, I then ran ‘fastboot flashing unlock’. I think this worked (because, when I restarted the phone, I had to go through the whole initialization process again).
The next step is where I ran into the problem. The first time, I put the modified init_boot.img in a new folder on the C: drive, but when I ran ‘fastboot flash init_boot path/to/magisk_patched.img’, I got the error “fastboot: error: cannot load <patched file>: permission denied”. So, then I copied the file to a folder on D:, ran the same command, and got the same error.
I suspect that I missed a step or something equally silly. Any suggestions as to what I should try or any pointers to other rooting guides that might be helpful? Don’t know if this means anything, but when the phone was powered off and plugged into the computer, I tried ‘adb reboot bootloader’ but nothing happened.

When you reboot, do you get the orange triangle with exclamation in it?
it might just be easier to move the magisk_patched.img to the platform-tools folder (the same folder that has adb.exe and fastboot.exe); if you are having "permission" issues from Windows, but you aren't from adb or fastboot, then supposedly having it in the same folder should run it under the same permissions.
Also, make sure that you run CMD as an elevated prompt; search for CMD, right-click, and "Run as administrator" -- this might help with the permission issues as well.
Final suggestion is to be sure to run platform-tools version r33.0.3...
Good luck and hope this helps...
P.S. Also, you might've had better luck and/or it's better organized if you posted in the Pixel 7 Pro (cheetah) forum instead of the Pixel 7 (panther)....

Use Pixel Flasher. Less hassle, more convenience.