I tried asking in the Boot Image thread but since that thread was originally posted in January, I dont think anyone even goes in there anymore. OK this is what Ive got.
Im not sure if it was the new radio update or the JF1.5 or 1.51 but ever since Ive upgraded from RC33 the fastboot screen has changed and I havent been able to change my Boot Image.
Instead of just connecting the phone to the computer and pressing back to get fastboot it now give me 4 options instead of just fastboot.Up top it says
FASTBOOT USB (highlighted in red) then
<CAMERA STEP2> HBoot Mode
<SEND> Reset Device
<ACTION> Restart to HBoot
<MENU> Power Down
Is there a new driver i have to download? or is it something else? because when i go to RUN/CMD and I type in the correct commands to change the Boot Image it does nothing it says <waiting for device>
I'm Sorry if this may seem like a dumb Q? but I figured maybe I wasn't the only one having this problem?
sorry I dont really know the answer man, sounds like you are using a new spl or some other bootloader. However, just to let you know, you really needed to post this in the dev section and not the theme section. you probably would get a better response over there.
Stericson
un install your phones drivers in device manager.
unplug your phone,
reboot your computer into safe mode.
plug your phone into usb.
a dialog box will pop up, navigate it to the sdk folder or wherever you have the g1 drivers. install them. wait till it finishes.
then unplug your phone and boot it into fastboot mode. the plug it back in again. and install the same drivers again
unplug your phone and reboot your computer. you should be able to access your phone in fast boot now.
dont push boot images in safe mode, it may be unstable
Thanx guys let me see what i can do
Editk i must have updated to another SPL so i went back to the Original HardSpl and it came back thanx stericson fo the Idea. back to normal
Message to MODS: you can close this if you want I'm sorry for wasting space
Hi,
There is a new driver for the usb connection.
Unzip this file to a folder and plug in your phone don't Mount .
The computer should ask for a driver.
if it doesn't look in control panel, system, usb controllers.
One of the devices will should a problem, update the driver with the files you downloaded and you should be ok.
The computer doesn't recognize the new bootloader until you update the driver.
When you then plug in your phone, it will say fastboot usb.
LatinSilEighty said:
Thanx guys let me see what i can do
Editk i must have updated to another SPL so i went back to the Original HardSpl and it came back thanx stericson fo the Idea. back to normal
Message to MODS: you can close this if you want I'm sorry for wasting space
Click to expand...
Click to collapse
LatinSilEighty said:
I tried asking in the Boot Image thread but since that thread was originally posted in January, I dont think anyone even goes in there anymore. OK this is what Ive got.
Im not sure if it was the new radio update or the JF1.5 or 1.51 but ever since Ive upgraded from RC33 the fastboot screen has changed and I havent been able to change my Boot Image.
Instead of just connecting the phone to the computer and pressing back to get fastboot it now give me 4 options instead of just fastboot.Up top it says
FASTBOOT USB (highlighted in red) then
<CAMERA STEP2> HBoot Mode
<SEND> Reset Device
<ACTION> Restart to HBoot
<MENU> Power Down
Is there a new driver i have to download? or is it something else? because when i go to RUN/CMD and I type in the correct commands to change the Boot Image it does nothing it says <waiting for device>
I'm Sorry if this may seem like a dumb Q? but I figured maybe I wasn't the only one having this problem?
Click to expand...
Click to collapse
the spl you have there is Haykuro's Custom SPL
I had the same trouble with getting fastboot to work
I did the same as you and went back to HardSPL
trying to find a way to get fastboot to work on the newer SPL tho
will update if i get it to work
Still in the process of flashing, but here is my fun experience of trying to un-root and having tried about 6 different methods I had an idiot savant moment and figured this out.
As the subject explains I had official 3.29.651.5 hboot 0.97.0000 that I used unrevoked 3.21 to root with clockworkmod 2.5 as the custom recovery.
I was trying to follow these instructions:
http://www.evo4gforum.net/htc-evo-4...emoval-of-root-restoring-stock-rom/?topicseen
and
http://forum.xda-developers.com/showthread.php?t=780141
and
countless others of flashing a pc36img.zip to restore a ruu version.
The problem with the first set of instructions is that I would get an Error 170 USB connection when the phone would reboot to the HTC bootloader.
The problem with the second set of instructions was that I kept getting an error of main version is older when trying to update from the recover power+vol down.
So what I got to finally work is:
download HTC Sync 2.40
Download from http://shipped-roms.com/shipped/Supersonic RUU_SuperSonic_S_Sprint_WWE_3.29.651.5_Radio_2.15.00.09.01_NV_1.77_CNV_release_150224_signed.exe
Windows 7 x64 Pro
1. Turn off the phone and power up using vol down + power
2. Start the RUU_SuperSonic installer and complete the first 2 check boxes and next. Once the box displays that its checking your phone for android version hit the first option which is fastboot
3. If it kick over to it fastboot usb since its still connected to the computer
4. If it gets to the USB Error connect on the PC, start over at 2 and try a different option under fastboot. I am not for certain if I hit boot loader under fastboot or not It took a few tries to get it to start the push from the PC.
5. Let it do its thing and it should complete the flash process like normal.
Downloading and updating to 3.70.651.1 right now.
Thanks, these steps worked for me. Very well written!
i think i just bricked my phone
i downloaded the RC2 rom, I have the bootstrap recovery and CWM and the unknown sourses app.
i was following your instructions on the dev release on how to install the rom
I downloaded the rom, put in on my sdcard i checked debugging usb
and then i hit the recovery bootstrap recovery button then the normal one ...
when it boots again i get critical error: CC00
DBAD
then another scren shows up with: Bootloader
09.12
Err:A5,70, 39,00,21
and i on the same screen it says: Battery: OK
OK to program
Connect USB
Data Cable
whe i conect the cable its says tranfermode: on
i dont know what to do at this point is there anything i could do to fix this?
I already tried yanking the battery out SDcard and put back in i just go back to the same screen
slowcurve said:
i think i just bricked my phone
i downloaded the RC2 rom, I have the bootstrap recovery and CWM and the unknown sourses app.
i was following your instructions on the dev release on how to install the rom
I downloaded the rom, put in on my sdcard i checked debugging usb
and then i hit the recovery bootstrap recovery button then the normal one ...
when it boots again i get critical error: CC00
DBAD
then another scren shows up with: Bootloader
09.12
Err:A5,70, 39,00,21
and i on the same screen it says: Battery: OK
OK to program
Connect USB
Data Cable
whe i conect the cable its says tranfermode: on
i dont know what to do at this point is there anything i could do to fix this?
I already tried yanking the battery out SDcard and put back in i just go back to the same screen
Click to expand...
Click to collapse
I just replied to your email, you efused!
This is exactly what happened to me when I bricked my gf's first bravo.
Good news is sbf and its fixed. You wont even lose any data.
IDK how this happens, seems it has happened twice now, there must be a specific change made before bootstraping that causes the check.
Either way the code group that is problematic is in the sbf, flash it and your good.
you will need to reroot, rerun nonmarket apps enabler, and re-bootstrap recovery, then reboto recovery and flash rc2 and you will be fine.
sorry for the spam... i panic'd..
i have the rsd lite i searched for sbf's and a whole bunch came up mind pointing which one i should use.
Edit: Its fixed thank you bando, you own half of my soul
Hi Guys,
I am a noob to xda so please bear with me...
Hoping someone can help me out here.. I will try and explain in as much detail as possible and provide you with as much Info from my phone as I can.
Firstly my phones details
Motorola Atrix 4g (UK version) Second phone as busted the last one. Bought outright as a retail sale.
Orange UK
System Version: 45.31.0.MB860.Retail.en.GB
Android Version: 2.3.4 (After UK released update)
Baseband Version: N_01.100.00R
Webtop Version: WT-1.2.0.133_38
Kernel Version: 2.66.32.9 [email protected]#2
Ok so, decided to root my phone. To do so I used petesMotorolaRootTools_V1.07 found on the website psouza4.com/bionic/
This worked fine and an app installed from the App Market confirmed that the phone was Rooted and had Superuser permissions.
Next I downloaded ClockWorkMod Rom Manager from the Market Inc Premium, SetCPU, Rom Toolbox & Titanium Backup Free. I had a quick look at these apps once downloaded but didnt really do a lot,
However, when Rom Manager opened it promted me to Flash ClockWorkMod Recovery, Which I did and then selected Back up current Rom. I also did this, (bear with me it gets a little vague here as to what I remember seeing)
Now I'm sure it said something like Nandroid Backup, which I selected. It proceeded to say something along the lines of, Backing up or phone will now reboot??
Anyhow, what ever it said, it started to reboot. The Motorola Red Circle logo came up but then at the top it said reboot failed and something ilse that didnt make sense then froze. I pulled the battery and rebooted. Seemed to work fine. Maybe a touch laggy but nothing to bad.
Next did my research into what ROM I'm likely to want to try. Found a few but seemed from what I have read on various forums that they dont work well for uk phones. Then decided perhaps then flashing should be left alone and went back to PetesMotorolaTools and unrooted. before I unrooted however i removed all apps that required root access first. Possibly a mistake?
I noticed that a few preinstalled apps werent working, nothing important or anything I use but there icons were like Blue settings icons all the same.
Did a factory reset through the handset also, in an attempt to return to factory settings.. not much changed really. Also tried to update software though the Motorola website but it said I was all up to date.
I thought maybe that something went wrong so I rooted again. This time the unroot failed. I then dowloaded all the rooted apps that I had before and then unrooted. This worked. Not sure if coincedence or not but it worked and when unrooting it said unfreezing apps about 6 times, before the complete message. Then uninstalled the root apps again.
Most, not all but most of those preinstalled apps were then working ok.
I read a little bit more bout Roms and decided to have another bash. Found and downloaded a few to comp. Then I place an SD card into phone and Flashed it. then tranferred a copy to its root.
Rooted the phone in the same way as before. Downloaded all the apps again opened CWM RM, Flashed CWM Recovery again as was unsure that the time I did it before would work. Then selected back up Current ROM. Without any message this time the phone started to reboot.
It came up with the recovery screen (Android man and !) From what I have read the next step is to tap the bottom right of the screen to bring up the menu.
This did not work nor did anything else happen. After waiting about 25mins with nothing more happening I pulled the batt again.
Decided I'd boot into recovery mode manually and see if the bottom right of screen would work that way. turned off then held On and down Vol. Fastboot showed at top, Scrolled and selected Android recovery. Same Android Man and ! came up, tried tapping the bottom right of screen again.... It didnt work.
Read more on the forums where someone said that pushing up and down on the Vol buttons works. Tried this and hey presto.. a new menu appears. Shown as follows.
Android system recovery <3e>
Android system recovery utility
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
No back up options so rebooted....
Anyway thought I'd try a few times to use CWM RM to flash a rom to device. Each time it took me throught this same process.
Eventually I though what the hec just try and flash it...
So I selected the apply update from sdcard option.
Then selected the ROM I saved to SD Card.
Then the following text appears on screen in yellow.
--Install /sdcard...
finding update package...
Openeing update package...
Verifying update package...
E:signature verification failed
Installation abborted
I tried this a few times to no avail. even tried downloading the roms from CWM RM with no change.
Read some more on the forums and somewhere read to rename the ROM update.zip
Did this and tried again.... No Joy!!!
Selected Fix permissions in an attempt to clean up and thats as far as I have got...
I'm at the end of my tether and dont know what to do...
Please, please, please someone help me get to the bottom of my dilemma..
Thanks for reading and any help in advance.
Just a little more info to help diagnose
CWM RM Details
Rom Manager Premium v4.8.1.3
Current Recovery: ClockworkMod 5.0.2.0
Latest Recover;ClockworkMod 5.0.2.0
Thanks again peoples for taking the time to at least read this..
No where in there did I see "I unlocked my bootloader"
That's fine that you're rooted, but to use CWM Recovery, install ROMs, make Nandroid Backups, etc. you need to unlock your bootloader first! See the international part of the Pudding thread (since your in UK) in the dev section.
Sent from my CM7 Atrix 4G
Ah Hah! You are correct at no point did I unlock my Booty, Thank you I shall give that a go and report back...
Ok so, I have trawled the forum and many others this avo on my research quest to unlock the bootloader as advised above but have been unsucessful so far.
I used the Pudding thread as you said.
when downloading the files advised I noticed that some were downloading as unrecognised files. I still proceeded to follow instructions as written.
Some of them like the RSD Lite I managed to unzip and extract with a programme I have however the next one needed said it was Undefined File type.
Anyway I deleted those files and tried following the other method listed underneath the driver via the link at "Guide for beginners provided by..."
This was unsucessfull as the "fastboot oem unlock" command was not recognised.
Pulled the batt and rebooted into normal mode and I'm back at SQ1
Bit stuck if anyone has any ideas..
Ok, here goes...
1) Make sure you have the drivers installed on your computer. (Available in Pudding Thread)
2) Go to pudding thread, and grab the Unlock Only IHOP sbf file (assuming your not on AT&T).
http://forum.xda-developers.com/showthread.php?t=1136261
"Unlock:
Unlocker only SBFs - These small 1mb SBF files will get your phone ready to fasboot oem unlock. They are the files most people should use.
ATT ONLY - Unlocker for 1.8.3 and 4.5.91 ATT firmwares
Orange/Bell/Telestra/Latin America/International users ONLY - Download IHOP"
3) Download & install RSD Lite. (Available in Pudding Thread)
4) Put phone in RSD Protocol Mode.
a) Power off phone
b) Upon Powering ON, hold Power Button + Volume UP
5) Connect Phone to computer via USB
6) unzip the IHOP sbf file to root of your C:\, open RSD Lite program, and drag sbf file onto File Name Box. Make sure RSD Lite sees your device connected to it, and then flash away.
7) After the sbf has flashed (hopefully without any errors), reboot your phone into fastboot mode (Power Button + Volume Down; when you see fastboot, press volume up to enter fastboot mode).
8) Re-connect phone to computer if you disconnected it.
9) In the folder where your fastboot files are located (if you don't have fastboot files, go download them from sticky in General Section), press Shift + Right Click, select Open Command Window Here.
10) With phone in fastboot mode, connected to PC and command window open in fastboot file location, type:
fastboot oem unlock
*This will give you your device #
Then type:
fastboot oem unlock [insert your # here]
10) Bootloader should unlock, then type fastboot reboot to reboot the phone. Should say Unlocked on boot screen now, if all went well.
11) Install Rom Racer's Recovery or Rom Manager, and you're good to go.
Think that about cover it... if you have any problems, give details of what is happening and at what step. Also, check the Pudding thread for possible solutions, as most problems have already been solved there.
Thank you for your explanation... I will give it a go when I get back from work tomorrow...
I appreciate you taking the time to help..
Sent from my MB860 using XDA App
Dcskeete said:
Thank you for your explanation... I will give it a go when I get back from work tomorrow...
I appreciate you taking the time to help..
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
You should definatly also install busybox
Swiftks said:
Ok, here goes...
1) Make sure you have the drivers installed on your computer. (Available in Pudding Thread)
2) Go to pudding thread, and grab the Unlock Only IHOP sbf file (assuming your not on AT&T).
http://forum.xda-developers.com/showthread.php?t=1136261
"Unlock:
Unlocker only SBFs - These small 1mb SBF files will get your phone ready to fasboot oem unlock. They are the files most people should use.
ATT ONLY - Unlocker for 1.8.3 and 4.5.91 ATT firmwares
Orange/Bell/Telestra/Latin America/International users ONLY - Download IHOP"
3) Download & install RSD Lite. (Available in Pudding Thread)
4) Put phone in RSD Protocol Mode.
a) Power off phone
b) Upon Powering ON, hold Power Button + Volume UP
5) Connect Phone to computer via USB
6) unzip the IHOP sbf file to root of your C:\, open RSD Lite program, and drag sbf file onto File Name Box. Make sure RSD Lite sees your device connected to it, and then flash away.
7) After the sbf has flashed (hopefully without any errors), reboot your phone into fastboot mode (Power Button + Volume Down; when you see fastboot, press volume up to enter fastboot mode).
8) Re-connect phone to computer if you disconnected it.
9) In the folder where your fastboot files are located (if you don't have fastboot files, go download them from sticky in General Section), press Shift + Right Click, select Open Command Window Here.
10) With phone in fastboot mode, connected to PC and command window open in fastboot file location, type:
fastboot oem unlock
*This will give you your device #
Then type:
fastboot oem unlock [insert your # here]
10) Bootloader should unlock, then type fastboot reboot to reboot the phone. Should say Unlocked on boot screen now, if all went well.
11) Install Rom Racer's Recovery or Rom Manager, and you're good to go.
Think that about cover it... if you have any problems, give details of what is happening and at what step. Also, check the Pudding thread for possible solutions, as most problems have already been solved there.
Click to expand...
Click to collapse
A BIG THANKS!!!
Thanks so much for the advice and instructions... Unlocked beautifully... Now to find the ideal ROM....
Dont suppose there are any suggestions for International (UK) Atrix users??
Really appriciate the help..
Regards
Danny
I would recommend that you flashed TWRP 2.0 through CWM direct link. It lets you have touch screen in recovery; much easier! Then if you like CM7 you could try this or if you like the MIUI style (like me!) you would want to try this! It hasn't in-game audio yet but it's much cooler in my opinion. But Neutrino CM7 is really great!
Im not sure, maybe someone else can confirm. You should be using moto-fastboot to unlock & not regular fastboot, right?
Sent from my MB860 using xda premium
draken_1337 said:
I would recommend that you flashed TWRP 2.0 through CWM direct link. It lets you have touch screen in recovery; much easier! Then if you like CM7 you could try this or if you like the MIUI style (like me!) you would want to try this! It hasn't in-game audio yet but it's much cooler in my opinion. But Neutrino CM7 is really great!
Click to expand...
Click to collapse
People have had problems with TWRP.............stick with Romracers CWM, it's tried and trusted. If the touch screen in CWM gets you off, so be it, but I'd rather have a recovery that works with all ROM's, and not just some.
Hi all,
First message in this wonderful community.
Anywas, having owned a Galaxy Note 3 for a few years now I thought I'd give it a shot at installing a new ROM to get it in better shape and try to stay with it a bit longer. Nothing really wrong with the phone other than getting a bit sloooow, specially the camera.
Anyways, not being a very geeky person, I soon realized the learning curve is steep.
This is what I've done so far:
1) Identified the model (SM-N9005)
2) Downloaded and unzip the SDK platform tools
3) Downloaded the TWRP custom recovery
4) Unlocked developer tools, allow unknown source (not sure if that is needed) and allowed USB debugging. In this phone I think there is no option for OEM unlocking.
5) Installed latest Samsung USB driver
5) Tried to proceed with unlocking the bootloader. This is where I ran into issues:
- I installed ADB Installer saying YES to everything
- Connected phone to pc with a usb cable
- From the command prompt (in my user) I executed adb reboot bootloader. I initially got an error (something about daemon and a port?....) but was able to move ahead
- The green android logo appeared along with this message "Downloading ...Do not turn off target!!"
At this point, pressing the volume down, power and select at the same time I tried to get out but kept on coming back to the same android menu stuck in "Downloading ...Do not turn off target!!". After the third try, a new warning message came up asking me if I want to proceed or reboot phone (pressing volume down) and I rebooted the phone to "escape" this predicament. I thought I was going to brick the thing!
Anyways, any recommendations on how to proceed? Is there an easier method to root the phone? Or to circumvent the issue I encountered?
As you might have guessed by my message, I can (sometimes) follow instructions but the underlying knowledge of what I am doing is .... well ...missing? :silly:
Hope you guys can help me. Thank you all in advance for your assistance.
PierreBCN said:
Hi all,
First message in this wonderful community.
Anywas, having owned a Galaxy Note 3 for a few years now I thought I'd give it a shot at installing a new ROM to get it in better shape and try to stay with it a bit longer. Nothing really wrong with the phone other than getting a bit sloooow, specially the camera.
Anyways, not being a very geeky person, I soon realized the learning curve is steep.
This is what I've done so far:
1) Identified the model (SM-N9005)
2) Downloaded and unzip the SDK platform tools
3) Downloaded the TWRP custom recovery
4) Unlocked developer tools, allow unknown source (not sure if that is needed) and allowed USB debugging. In this phone I think there is no option for OEM unlocking.
5) Installed latest Samsung USB driver
5) Tried to proceed with unlocking the bootloader. This is where I ran into issues:
- I installed ADB Installer saying YES to everything
- Connected phone to pc with a usb cable
- From the command prompt (in my user) I executed adb reboot bootloader. I initially got an error (something about daemon and a port?....) but was able to move ahead
- The green android logo appeared along with this message "Downloading ...Do not turn off target!!"
At this point, pressing the volume down, power and select at the same time I tried to get out but kept on coming back to the same android menu stuck in "Downloading ...Do not turn off target!!". After the third try, a new warning message came up asking me if I want to proceed or reboot phone (pressing volume down) and I rebooted the phone to "escape" this predicament. I thought I was going to brick the thing!
Anyways, any recommendations on how to proceed? Is there an easier method to root the phone? Or to circumvent the issue I encountered?
As you might have guessed by my message, I can (sometimes) follow instructions but the underlying knowledge of what I am doing is .... well ...missing? :silly:
Hope you guys can help me. Thank you all in advance for your assistance.
Click to expand...
Click to collapse
flash custom recovery.download supersuzip latest version is 2.82.push it to your phone.reboot to recovery mode.flash supershu zip.reboot to system.your phone is rooted.that's it.
Sent from my SM-N930F using Tapatalk
Normal method .
Flash TWRP via Odin.Put custom rom on SD card .
Boot to TWRP recovery and flash .
N9005 does not have a locked bootloader .