Related
Alright, after spending hours upon hours researching multiple forums I can firmly say I'm stumped. As an FYI, I change ROM's frequently and have preformed these actions multiple times. So this isnt about me being a noob and doing something incorrect due to lack of knowledge (at least i hope not).
After multiple methods I can not find a single way to get into download mode.
Methods attempted:
1. cards and Battery out
waited up to 30 min with battery out,
battery in
hold volume buttons (tried to do this before the battery goes in as well)
usb plugged in (odin on in background of course)
I have gotten into download mode multiple times using this method, however, doing it now (and multiple variations, including holding only volume up or volume down, tapping power once and a bunch of random things people from various forums 'claim' to work) will result in only one thing; having the battery charging screen pop up and freeze on me. I know it is frozen as the progress timer is stuck at the 12:00 position and doesnt change, even if left there for an hour or two.
If the phone is allowed to power up normally (or i press the power button when trying to go into download mode) the phone will go to the standard ATT screen flash once then show up again and finally go into recovery mode. My research hasnt shown that i can do anything from recovery mode without having access to the internal SD.
upon further research, I came across only one other thread of e=people who had a similar problem, however the OP said he performed the download mode method mentioned above over and over and then it eventually worked. Which doesnt make a whole lot of sense to me, but nonetheless he said he got it within 40 times, I must have done this over 100 times now with the same frozen battery screen result.
I even tried ADB, which is something that was new to me. But after getting ADB to successfully work on the command line, it does not recognize that the phone is connected (my assumption is because in recovery mode, which is the only place i can be with the phone on besides the frozen screen, the internal SD isnt mounted for mass storage). So ADB didnt work either.
I am within my 30 day period, but of course, I would prefer to just fix this thing as opposed to going down to have 'the talk' about bricking my phone with ATT. Has anyone seen this issue? Anyone else have any ideas? Anything I can do from the recovery screen?
Thanks for your help
Adb should work in recovery mode.
Let me know 2 things: your batch #
What ROM you were using when it went out
Sent from my SAMSUNG-SGH-I897 using XDA App
PS don't tell att you modded your phone
Sent from my SAMSUNG-SGH-I897 using XDA App
Yea I had the same problem when i bricked my brothers captivate. I did all the 3 button method and i couldnt still go to download mode but i figured another way on how to get there =) thanks to me. But this method only works if your computer recognize your phone like if your stuck on atnt screen or galaxy s screen or even more if its all dark screen, but most importantly is that your computer recognize your phone and you have clockwork recovery. Here is the link of my post.
http://forum.xda-developers.com/showthread.php?t=842484
@fattire
1. Where do i locate the Batch #
2. It had just finished flashing into Cog 2.3b4. I had flashed to stock (like I normally do) before flashing to Cog. Looking at the screen, everything looked like it went fine and Cog was installed properly. After it finished it started restarting the phone, and this is where I am now.
P.S. Yeah, that goes without saying just so much of a hassle with the ATT people....
P.P.S. I didnt know if this was normal or not, but in recovery mode the computer can see the phone's drive but it (the phones drive) is not mounted so I can not access any of the files on it. From all that I have read ADB is working correctly and have confirmed it in the command line. I have the correct drivers ( and i know they are the right ones bc Ive done this before on the same computer with the same USB port). Odin also recognizes the phone and says it is connected but upon trying to flash to stock or anything else it just hangs, again my assumption is bc the internal SD is not mounted correctly...
@G1
Thank you for your suggestion, unfortunately it appears the phone is not being mounted correctly on my comp to recognize it properly. So your method will not work.
But keep the ideas coming!! Anyone else?
There's a solderless procedure to go in download mode.
http://forum.xda-developers.com/showthread.php?t=841512
@Silver
I attempted the procedure and it only resulted in the phone booting up to the att screen then going into recovery mode.
After this procedure, performing method 1 to get into download mode does not result in a stalled battery screen, it now goes into recovery mode. Maybe I fried something....
Oh well off to att tomorrow.....
madpuma13 said:
@fattire
1. Where do i locate the Batch #
Click to expand...
Click to collapse
Under your battery 100? number
madpuma13 said:
@Silver
I attempted the procedure and it only resulted in the phone booting up to the att screen then going into recovery mode.
After this procedure, performing method 1 to get into download mode does not result in a stalled battery screen, it now goes into recovery mode. Maybe I fried something....
Oh well off to att tomorrow.....
Click to expand...
Click to collapse
If you can get to recovery mode then your fine well it depends if you have clockwork recovery. Clockwork have an option that will take you to download mode.
Sent from my T-Mobile G2 using XDA App
Hey everyone. I figured id make an official thread,although a thread a few down is very similar but still quite different.
I attempted to re-lock my XOOM wifi and I got the error.
-only able to get into RSD mode 2 or Fastboot protocol
-pc will not recognize through adb or RSD 5.0
-tried various command and no luck
-Screen wont turn off unless battery dies.
- reinstalled sdk, drivers etc.
I might of missed a few details, but ive been all around the forums and have yet to see a solution for this other than send it to Motorola. Ha just curious to whether anyone could shed a little more light on this situation. Not being able to RSD or adb seems like a bad situation, even if we did have that darn sbf id still be stuck! Thanks guys!
Sent from my DROIDX using Tapatalk
Try to get the xoom back into fastboot by rebooting (vol up + power) and then immediately holding vol down + power until the fastboot screen comes up. From there try pushing system and boot .img's through fastboot. Then you should be able to reunlock from the fastboot command on your pc. There is no way that I know of to re-lock a wifi only xoom as of yet.
Yeah, my bootloader screen says that im "Starting Fastboot protocol service" but I get no response from my PC. I've never had problems with adb recognizing my xoom before this. Its like the drivers arent even compatible with the device anymore?? For craps i attempted to send some commands through adb even though it didnt recognize the device, and had no luck. ADB simply replies "waiting for device" for all of them.
try reloading your moto drivers
Make sure you aren't using a front panel port. I had thus problem for ages, XOOM is a power hog. As for the LNX failure its the result of relocking with an invalid image, don't do it.
Sent from my HTC Desire using Tapatalk
Yeah, i spent days trying to figure that one out with the front ports vs. the back ports with my droid. I could never get it to remount in RSD when flashing a .sbf.
Thanks for the heads up though. Im not sure what made me think that it would be ok. My failure to do some research always lands me in pretty much the same spot! Here.
I reloaded all the drivers ect and have been unable to get anything. My droid works great, but no xoom.
Had this exact thing happen to me today. What fixed it for me was
- boot into fastboot (Power+Vol Up then immediately hold Vol Down until you see it display the fastboot message) and push the stock boot/system images found all over this forum for your model (Wifi/3G)
Now obviously your ADB isn't seeing your device... neither was mine
- Go under Device Manager on your PC and uninstall your Motorola drivers from whatever devices are listed
- Do a fresh install of the Moto Drivers and restart your PC
- Run, 'fastboot oem lock' to allow RSD to do it's work
That's what it took for me. If that fails, unplug your Xoom from the PC and set to debug mode, then plug back in and let Windows find your drivers. Windows could take some time, and actually took me unplugging/replugging twice until it decided it found them.
RSD is a load of junk, but when it works it's like the miracle worker =P Good luck and keep your head up! These things are harder than people think to completely wreck =)
Xezuka said:
Had this exact thing happen to me today. What fixed it for me was
- boot into fastboot (Power+Vol Up then immediately hold Vol Down until you see it display the fastboot message) and push the stock boot/system images found all over this forum for your model (Wifi/3G)
Now obviously your ADB isn't seeing your device... neither was mine
- Go under Device Manager on your PC and uninstall your Motorola drivers from whatever devices are listed
- Do a fresh install of the Moto Drivers and restart your PC
- Run, 'fastboot oem lock' to allow RSD to do it's work
That's what it took for me. If that fails, unplug your Xoom from the PC and set to debug mode, then plug back in and let Windows find your drivers. Windows could take some time, and actually took me unplugging/replugging twice until it decided it found them.
RSD is a load of junk, but when it works it's like the miracle worker =P Good luck and keep your head up! These things are harder than people think to completely wreck =)
Click to expand...
Click to collapse
Just curiousity, if we can't boot our xoom, how can we enable USB debug mode?
This is the same of my problem:
http://forum.xda-developers.com/showthread.php?t=1052762
tritran18518 said:
Just curiousity, if we can't boot our xoom, how can we enable USB debug mode?
Click to expand...
Click to collapse
Sorry I guess I didn't mean to set it to Debug from the Xoom, but as in to remove it and boot into Fastboot. Then plug it back in and allow Windows to install the drivers.
I had a hard time getting it to work, but after uninstalling and reinstalling the drivers, it recognized it and allowed me to flash the SBF.
Correct me if I'm wrong here! It's what worked for me. My Xoom went down like this and I resurrected it this way. Been working flawlessly on Tiamat 1.3.1 ever since.
Sorry guys, but the condition I'm in is becoming popular lately. I'm able to get the XOOM wi/fi to show "starting fastboot protocol" but absolutley no recognition on the pc. RSD or ADB. Therefore all commands sent from the ADB simply respond with "waiting for device" and unable to flash any images onto the device. Its in a real brick mode. At least for the time being with the lack of software communication on the pc and no .sbf yet. I sent the device into motorola for repair. They said the repair would be under the warranty and free of cost. I was honest as well, telling the repp I had unlocked the device and attempted to re-lock. Thanks for all the suggestions and input guys.
follow up?
hello i am curious what happened with your returned brick? did moto replace it?
I ask because i have the exact same issue and have gone through all the suggestions.
same error, cannot get into fastboot, no adb, no RSD, nothing. tried the various vol power button combos etc. no recognition on PC at all. yes i re-installed drivers etc etc etc... i have been reading...
it seems only option is to wait on SBF or return?
Yeah the only solution would be an sbf flash. But even with that i do not know how because the RSD lite does not recognize the device either.I simply placed an order online, they sent a box the next day, sent it and got it back in two days. Extremely fast. I told the tech rep over the phone that i had unlocked the device and and then downloaded an app that starting causing for restarts and so i attempted to re-lock the device and from there it was officially a true brick. I was honest and they seem to be very understanding. Im sure they understand that the lack of support for the device is evident and we are all beta testers. SO let em know whats going on. I also let him know i was a developer, whether it mattered or not i dont know, but i was just being honest. Its all covered under warranty he said. I didnt pay a penny
OK well its good to know I am totally screwed!!! thanks for the reply...
I told the rep on the phone what I did but I don't think he had any clue what I was talking about... he asked to me to reboot with vol up, then try to boot into fastboot, but didn't once say fastboot, just said vol down, then said he would send me a shipping box.
Get it today!!
I am in this situation after trying to re-lock in order to install the 3.1 update. I tried re-installing and updating the Moto drivers, rebooting etc but I can't get my PC to recognise the device in fastboot or RSD. I am on a stock Canadian ROM (but unlocked obviously).
I have sent an email to Motorola and been honest with them. Will see what they say.
That's the thing - moto provides all the tools to relock for US ONLY! There is no official way for canadians, which makes no sense. So us canadians can unlock no problem, but cannot relock, yet US units can? Strange to me...
chaz03 said:
Yeah the only solution would be an sbf flash. But even with that i do not know how because the RSD lite does not recognize the device either.I simply placed an order online, they sent a box the next day, sent it and got it back in two days. Extremely fast. I told the tech rep over the phone that i had unlocked the device and and then downloaded an app that starting causing for restarts and so i attempted to re-lock the device and from there it was officially a true brick. I was honest and they seem to be very understanding. Im sure they understand that the lack of support for the device is evident and we are all beta testers. SO let em know whats going on. I also let him know i was a developer, whether it mattered or not i dont know, but i was just being honest. Its all covered under warranty he said. I didnt pay a penny
Click to expand...
Click to collapse
Try rsdlite 4.9 or earlier it should see it then.
I tried RSD 4.9 and no luck. I think it just doesn't work with Wi-Fi only zooms.
Sent from my Nexus S using XDA App
footboydog said:
I tried RSD 4.9 and no luck. I think it just doesn't work with Wi-Fi only zooms.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Anyone who locked the zoom back and now can't boot, try my instructions from another thread...
1) Turn the xoom on and leave it plugged into USB. 2) When it says Starting RSD Mode 2, type the following in your command prompt in windows "fastboot oem unlock"
*Make sure you are typing these commands within the directory where your fastboot and .img's are located. ( I dropped mine in C:\Android-sdk\platform-tools\*The Xoom will not respond initially and your command prompt will say "waiting for device".
3) Hold the power button and volume up to reset the xoom. The fastboot command should intercept the xoom booting and take you to the unlock prompt again. Follow the on screen instruction.
*This will wipe the device again, which I'm assuming you did when you locked it with a custom kernel (boot.img)
After it is completed, type "fastboot reboot" in windows command prompt or just reboot however you can.
crushsuitandtie said:
Anyone who locked the zoom back and now can't boot, try my instructions from another thread...
1) Turn the xoom on and leave it plugged into USB. 2) When it says Starting RSD Mode 2, type the following in your command prompt in windows "fastboot oem unlock"
*Make sure you are typing these commands within the directory where your fastboot and .img's are located. ( I dropped mine in C:\Android-sdk\platform-tools\*The Xoom will not respond initially and your command prompt will say "waiting for device".
3) Hold the power button and volume up to reset the xoom. The fastboot command should intercept the xoom booting and take you to the unlock prompt again. Follow the on screen instruction.
*This will wipe the device again, which I'm assuming you did when you locked it with a custom kernel (boot.img)
After it is completed, type "fastboot reboot" in windows command prompt or just reboot however you can.
Click to expand...
Click to collapse
I have just tried this and still no luck. Fastboot just sits there with the "waiting for device" message and the Xoom just boots with the "Starting RSD mode 2" message. I also tried your suggestion with rebooting into fastboot mode by holding the vol down button and that doesn't work either.
BTW I don't have a custom boot.img. I am on a stock ROM but I just had the bootloader unlocked.
Incidentally I have tried RSD lite 4.8, 4.9 and 5.0 now and none work.
So I got bored with waiting around for someone else to do it, and decided to take a shot at rooting my G-Slate. I figure it's basically the same as the Xoom, so the same sort of process should work....
My initial game plan was this:
Get into Fastboot
Flash a recovery image
Boot the recovery image
Now "adb shell" is a root shell
Copy a "su" binary into /system/bin
Declare victory
That started out pretty well. Powering on and holding down volume-up gets into fastboot. The fastboot binary on my laptop sees the device. Typing "fastboot oem unlock" claims to work. Flashing the Xoom recovery image [1] claims to work.
But... I can't seem to boot to recovery. Running "adb reboot recovery" just reboots normally. Doing "fastboot boot recovery.img" freezes the device. Booting with down-volume gets me to some sort of LG updater state that might as well be freezing the device. Booting with both volume buttons down either 1.) doesn't boot or 2.) brings me to fastboot. That's all the button combinations.
So I guess my question is this: does anyone have any suggestions for how to proceed?
I really don't want to just blind-flash the Xoom boot.img from the unlock thread, because if that doesn't work my device is bricked until someone either makes a working kernel or somehow extracts the current one.
On the up side, my g-slate is *claiming* to have working fastboot that can flash images. It could be totally lying though.
[1] http://forum.xda-developers.com/showthread.php?t=1038870
Tried the same method. No dice. Right now there has been no luck on anyone's part that i know when it comes to rooting. Shoot we havent even been able to get one of the xda mods to create us our own forum for that matter...i had to go out and create my own. I have tried other methods that worked on my nexus one when none other would but alas still no luck.
I imagine since the g-slate is brand new that its not a question of if it can be rooted, but how and when. I'm going to try one more method i know of that worked on the lg optimus tonight. I'll post here if it works.
Soure code seems to be available too
It also appears the source code is available from LG here .lg.com/global/support/opensource/opensource-detail.jsp
I just did a search under mobile phones for the model number 909
Don't know if that will help anyone here.
I have been hunting all over for root access. fastboot says I unlocked the bootloader but nothing seems to want to take.
XDA Mods, please create a G-Slate Section
HA. member since 2006 and my first post just add a www in front of that link
When the fastboot says Ok it is not telling you that you have unlocked the device. It says ok no matter what you put in. Try unlock and it will say ok as well. If it unlocked the device then it would prompt you on your device with a popup that tells you that you are voiding your warranty and have you hit ok. The device is not unlockable using the 'fastboot oem unlock' command. I have rooted a lot of devices, but never have done anything on an LG device and it is awkward. Vol+ and power gets some form of fastboot. Vol- and power gets download mode, which I am used to from Samsung devices (if we can get an interface like Odin then this becomes a lifesaver and makes the device "virtually" unbrickable). I cannot find any form of recovery. 'Adb reboot recovery' just restarts the device. One interesting this is that pushing both Vol+ and Vol- and power puts the device into what would seem like a bricked device (just use reset button). This same button combination worked on some Samsung devices so something is happening there, but I have not tried enough combos yet to figure it out.
So far as root, well, I have tried z4 (works with nearly all Sammy devices and LG seems to be using a lot of Sammy ideas or at least it looks that way), but to no avail. Gingerbreak apk might work or even the Xoom Root, but the rootboot.img might be different and I have not opened any of that up yet. I did get SU loaded once and in the system, but I could not reproduce it.
I will be working on this some more this weekend (returning the device at some point as it reboots on its own about 5 times a day), and looking into the recovery issue. If anyone has any ideas then please post.
Also, it looks like LG hacked the crap out of the thing to get the SD card to mount and it is weird, so please be aware of that. The SD card mounts every time you plug the device in and there is no way to turn that off. The reason this is important is that some root methods require that the SD card not be mounted, so you will have to unmount the SD card via ADB and with the card being internal I am not too sure it is a good idea, but . . .
I will mark this thread as a favorite and update if I get any where. I know that Cyanogen and Kmobs got G-Slate's recently, so hopefully they can give us a little insight once the device gets to them. I have also contacted LG and @TheLGGirl and asked them to confirm that the bootloader is locked, but have not heard anything back.
Also, the the Acer HC tablet was rooted yesterday using the Gingerbreak root method, and so that is helpful, but it has an SD card (see above).
Sent from my LG-V909 using Tapatalk
I tried the Acer method (GingerBreak) and it does not work. Will look at the logcat in a bit.
Sent from my LG-V909 using Tapatalk
Thanks hourst
I am used to odin (also have a vibrant). Something like that would be a life saver.
Makes sense about the fastboot commands seeming to take.
I was also having reboot issues with mine. I had a handful of reboots each day (about 3 or 4) for the first two days but they have stopped completely now. I have had it for about a week now and have not noticed a reboot since day 2.
I will keep poking around to see if i can come up with anything as well.
Could this help?
Under the impression the G2x root method maybe helpful since they are both LG devices with somewhat similar hardware.
Does anyone know or tried this http://forum.xda-developers.com/showthread.php?t=1056847 to see if it works?
Not sure if I am brave enough yet. But it could be possible the vol up+vol down+power button combo that seems to lock the device is putting it into the mode needed to run the nvflash application.
This really is mostly speculation but could be something to try.
Success
So i got brave.
vol up+vol down+power Device seems to freeze. Plugged in the usb and got a new hardware pop in windows. Listed it as APX device using the drivers in the file listed in my previous link installed successful and the device was found.
That is a far as I went.
im doing the NVFLASH right now... wish me luck and see how far I can go
Any Luck?
Suzannemscott
How did it go? any results or do you have a large brick?
ok i tried. and no luck , i did manage to brick it tho, but i was able to unbrick it phew, back to square one
Did it seem like anything happened? Also what did you do to unbrick it?
To unbrick it i just press the reset button, in the back, quickly hold down Vol+ and Vol- then it goes to a the Gslate screen with the square and then i hold down the reset again and it reboots, maybe i am doin to much but hey it get my Tab back it works!
Gah! Why does it claim to have fastboot when *any* fastboot command except "fastboot devices" just makes it freeze?
I went ahead and built the kernel that LG released and packed it into the clockwork recovery image for the Xoom. Fastboot boot... freeze.
Computer always says this, but I think it's just making fun of me:
downloading 'boot.img'... OKAY
booting... OKAY
I also tried to build and boot a custom kernel with a fb console enabled just to get some feedback, but all it wants to do in response to "fastboot boot" is freeze.
I'm starting to get discouraged here. My 14 day return period ends on Tuesday and I don't really want to get stuck with an unrootable device.
Chandon, would you be able to send me the kernel you built?
I'm sure someone with more expertise and knowledge will be able to root this thing eventually...but right now it seems to be a lot trickier to root than I initially thought. It's not unrootable...just complicated. Over my head by a lot. I don't think I'm going to return it...but I've now resigned to the fact that I may not ever be able to find a working method to root the damn thing myself.
SmellyTunic -
I've uploaded the two kernels I built [1].
They're both built from the v909 kernel source posted by LG[2], following the instructions posted by adrynalyne[3] for building custom android kernels, but I don't have any way to test them aside from the fact that "fastboot boot" doesn't work either straight, with a ramdisk, or with a rebuilt recovery image using the tools in [4].
[1] http://pandion.ferrus.net/gslate/kernels
[2] http://opensource.lge.com
[3] http://forum.xda-developers.com/showthread.php?t=1039854
[4] http://forum.xda-developers.com/showthread.php?t=915808
hourst2 said:
When the fastboot says Ok it is not telling you that you have unlocked the device. It says ok no matter what you put in. Try unlock and it will say ok as well. If it unlocked the device then it would prompt you on your device with a popup that tells you that you are voiding your warranty and have you hit ok. The device is not unlockable using the 'fastboot oem unlock' command.
Click to expand...
Click to collapse
Not entirely true. You said that if you try simply typing in "fastboot unlock", it tells you "OK" as well, right?
Not for me. That only ended up displaying the whole list of fastboot commands.
I agree with you that "fastboot oem unlock" is not unlocking the device though. But what are the alternatives? Everything I've ever rooted has used "oem unlock". I've never even heard of a different command that can be used to unlock a bootloader. I tried a google search and came up with nada.
Hmm...
wich you the best make happen
Been modding android devices since the G1 but never got stuck like this before. Already spent hours of searching and googling but couldn't find any definite answer.
My B70 got bricked when using a program to boot into recovery.
Is there any way out or should I just throw it away?
I have a feeling that the device is looking for a recovery on internal SD card and fails. I can see the unit as ADB unit but when trying to connect it says device is offline both in normal boot or in recovery boot.
Been trying putting stock roms on external SD but it never runs it.
Has anyone solved this problem?
Check your SBK version and try to NVFlash
Try to boot recovery/apx wipe permissions /data if possible
post questions in Q&A not Dev
After a lot of examination it has been decided that you have posted this in the wrong section and we shall place it where it should be. Please make sure you post correctly next time.
Like mentioned already, some B70 are SBKv1 meaning nvflashable.
What app did you use to get into recovery causing the "brick"
Can you still get into cwm recovery, ect.
you still have hope if ADB can see it, try to update your driver.
If it work use ADB to push the file you need.
Sorry for wrong thread.
I probably have SBK2 (how to check) because usb just disconnects as soon as I try to run any nvflash stuff.
I also believe that ADB could be the saviour but it says offline. So this could be due to driver issue? Interesting, I shall try on a 32 bit computer.
If I suceed to connect through ADB, can I then flash CWM recovery?
The app I used to get into recovery was just a random boot into recovery app. It worked many times before. I don't think taht app caused this, maybe the recovery files where deleted?
df9517 said:
Sorry for wrong thread.
I probably have SBK2 (how to check) because usb just disconnects as soon as I try to run any nvflash stuff.
I also believe that ADB could be the saviour but it says offline. So this could be due to driver issue? Interesting, I shall try on a 32 bit computer.
If I suceed to connect through ADB, can I then flash CWM recovery?
Click to expand...
Click to collapse
You can use SBKdetect to check your SBK version (linux)
Did you have CWM before? Are you rooted?
What is your tablet doing right now? Stuck at the start up screen?
My tablet was previously running rooted ICS WW .11 with CWM.
Now its just stuck at the first boot image. I can go into same image where it tries to run recovery image by holding vol down. I guess it is standard brick.
Not getting anywhere with ADB, device is offline
hmm.. can you cold boot? just hold vol-down and wait?
df9517 said:
Not getting anywhere with ADB, device is offline
Click to expand...
Click to collapse
Search on here for the universal naked driver. Try that or sometime if you can try a different usb port.
Can you get into CWM Manually?
Hold VOL DOWN and POWER for about 10-12 seconds until some small text appears.
Quickly (within 5 seconds) release both buttons and hit VOL UP to enter RCK (Recovery).
If you can get into CWM this way you should be able to clear some caches and see if it will boot. If need be, you may be able to flash a new ROM if need be.
I only got the naked ADB drivers to work. The real ASUS ones does not work. Only tries 64 bit though.
Of course I tried to go into recovery manually.
Actually I now remember that just before this happened I updated CWM through the clockwork app. Probably updated to a version that does not work.
Since you have ADB working, download a CWM flashable .zip from your favorite recovery thread and extract the recoveryblob.
adb push it to /temp/dd or something similar, then run adb shell, su, and (you will need root/busybox on here) dd if=/your/blob/here of=/dev/block/mmcblk0p4.
after running that, run reboot, you should see a blue line and be able to get into a good CWM recovery. never use rom manager.
Thing O doom.
It always says my device is offline using ADB. I have only got naked driver to work.
But now I saw the NVflash for B70+ devices in your post. I will try that tonight.
I have not given up.
Yes, that is probably your only hope if you can't get ADB working, and it just came out! Lucky day
Yes, thank you all!! Finally NVflash for B70+ devices saved my day. Reflashed original ROM.
It's midnight and I'm getting frustrated. I've been wanting to root my phone, but I can't even seem to unlock the bootloader. To start, I followed the instructions in the Backup Partition/renoroot thread , and I managed to do the first bit fine. Instead of using the Flashtool the OP of the pdf did, I went with the Minimal ADB Fastboot app instead. When I plug the cord into my phone while holding the Volume Up button, everything seems to go fine. I get the blue LED just like all the instructions say. But then I go to fastboot through the command prompt, but nothing happens. I even tried to do the final step in the official Sony guide, and it just gave me "waiting for any device". What am I doing wrong? Have I missed a driver somewhere?
Nevermind, I just used Flashtool while my PC was booted to allow unsigned drivers. Don't know why I didn't do that earlier. Sorry everyone.