Database Info

Stuck Rooting @ tf300t

hi guys,
i was following this thread guide http://forum.xda-developers.com/showthread.php?t=1668173
and while i'm on step 5, i accidentally pick the wipe data (available options are RCK, Android and Wipe Data)
now, i am stuck in this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and totally unable to mount sdcard, emmc. Hopefully my tablet hasn't bricked yet.

johnson234 said:
hi guys,
i was following this thread guide http://forum.xda-developers.com/showthread.php?t=1668173
and while i'm on step 5, i accidentally pick the wipe data (available options are RCK, Android and Wipe Data)
now, i am stuck in this View attachment 2454401 and totally unable to mount sdcard, emmc. Hopefully my tablet hasn't bricked yet.
Click to expand...
Click to collapse
I remember on the old bootloader that ended in and insta-brick, but idk which BL you are on.

cmendonc2 said:
I remember on the old bootloader that ended in and insta-brick, but idk which BL you are on.
Click to expand...
Click to collapse
By BL u mean bootloader? My stock bootloader is 4.2.1 Jelly Bean. I tried to dl the twrp.blob from the twrp website with -4.2 and try to use the terminal emulator thingy but it still boot into CWM based Recovery.
However, I just bought the ROM Toolbox Pro in Google Play and use the 'Flash Recovery' but it search my whole tablet and returns nothing while i have already copy and paste the twrp.blob into the/sdcard/

johnson234 said:
By BL u mean bootloader? My stock bootloader is 4.2.1 Jelly Bean. I tried to dl the twrp.blob from the twrp website with -4.2 and try to use the terminal emulator thingy but it still boot into CWM based Recovery.
However, I just bought the ROM Toolbox Pro in Google Play and use the 'Flash Recovery' but it search my whole tablet and returns nothing while i have already copy and paste the twrp.blob into the/sdcard/
Click to expand...
Click to collapse
Edit: I am a first timer a.k.a. newbie. Sorry for that if i don't understand the short form/ slang u used.

johnson234 said:
By BL u mean bootloader? My stock bootloader is 4.2.1 Jelly Bean. I tried to dl the twrp.blob from the twrp website with -4.2 and try to use the terminal emulator thingy but it still boot into CWM based Recovery.
However, I just bought the ROM Toolbox Pro in Google Play and use the 'Flash Recovery' but it search my whole tablet and returns nothing while i have already copy and paste the twrp.blob into the/sdcard/
Click to expand...
Click to collapse
Wait it boots into android? What exactly are you trying to do? Just install the Superuser binaries for root or get a custom ROM?

cmendonc2 said:
Wait it boots into android? What exactly are you trying to do? Just install the Superuser binaries for root or get a custom ROM?
Click to expand...
Click to collapse
I plan to root it into a custom rom but ended up installing cwm which I later found out to be incompatible with my device. This is because I thought that everyone need to undergo these three process (root>install recovery>install rom) now I'm trying to remove or replace this cwm with a twrp then I can start installing my custom rom. I have already root my tablet with supersu (kingo). Did I do anything wrong on my steps above? If yes, please enlighten me. Thanks
anyway, what's a super user binary?

johnson234 said:
I plan to root it into a custom rom but ended up installing cwm which I later found out to be incompatible with my device. This is because I thought that everyone need to undergo these three process (root>install recovery>install rom) now I'm trying to remove or replace this cwm with a twrp then I can start installing my custom rom. I have already root my tablet with supersu (kingo). Did I do anything wrong on my steps above? If yes, please enlighten me. Thanks
anyway, what's a super user binary?
Click to expand...
Click to collapse
OK download the -42 TWRP recovery for jellybean onto your computer. Use fastboot (http://forum.xda-developers.com/showthread.php?p=42407269) to flash the bootloader to your tablet with:
Code:
fastboot flash recovery TWRP.img -i 0x0b05
Then reboot into Android and reboot again into TWRP to flash a custom ROM.

cmendonc2 said:
OK download the -42 TWRP recovery for jellybean onto your computer. Use fastboot (http://forum.xda-developers.com/showthread.php?p=42407269) to flash the bootloader to your tablet with:
Code:
fastboot flash recovery TWRP.img -i 0x0b05
Then reboot into Android and reboot again into TWRP to flash a custom ROM.
Click to expand...
Click to collapse
Sorry to tell you but everytime i try to fastboot, (tried this even before posting the problem here) i get this error. Waiting for like 10mins, the 'waiting for device' message is still there.
Command I used,
fastboot flash recovery TWRP.img -i 0x0b05
Click to expand...
Click to collapse
After pressing enter, i get this
< waiting for device >
Click to expand...
Click to collapse
Edit; sorry for the screenshot, typed the command wrong but tried it with the correct 1 but the outcome still the same.

I'm thinking that is it usb drivers problem? currently running on Win8 Professional 64bit.

johnson234 said:
I'm thinking that is it usb drivers problem? currently running on Win8 Professional 64bit.
Click to expand...
Click to collapse
Fastboot utility is very sensitive to connection type. It can refuse to work on some laptops and usb ports on front pannel of desktop PC. Also do not use usb hub or tablet dock with fastboot. And if Windows device manager shows tablet as something like "asus bootloader interface" or "asus fastboot interface" (don't remember exact name) is probably shouldn't be a driver issue.

Graiden05 said:
Fastboot utility is very sensitive to connection type. It can refuse to work on some laptops and usb ports on front pannel of desktop PC. Also do not use usb hub or tablet dock with fastboot. And if Windows device manager shows tablet as something like "asus bootloader interface" or "asus fastboot interface" (don't remember exact name) is probably shouldn't be a driver issue.
Click to expand...
Click to collapse
It has these 2 (see attachment) and I even can use ASUS SYNC perfectly. So i guess the usb driver wont be a problem?

johnson234 said:
It has these 2 (see attachment) and I even can use ASUS SYNC perfectly. So i guess the usb driver wont be a problem?
View attachment 2457522
Click to expand...
Click to collapse
Did You know that to use fastboot tablet should be loaded in fastboot mode? If You connect it in fastboot mode and Windows shows no recognised fastboot or bootloader interface You need a proper driver.

So, you suggest that i need to use a different pc to do the fastboot thing? What are the drivers do i need to install? Where can i download it? Maybe my wind8 64bit professional got some flaw/bug. Thanks for helping. Will try it out when i get back home.

cmendonc2 said:
OK download the -42 TWRP recovery for jellybean onto your computer. Use fastboot (http://forum.xda-developers.com/showthread.php?p=42407269) to flash the bootloader to your tablet with:
Code:
fastboot flash recovery TWRP.img -i 0x0b05
Then reboot into Android and reboot again into TWRP to flash a custom ROM.
Click to expand...
Click to collapse
I get something like this. But when i reboot into android and reboot it, i still get boot into CWM recovery. Nothing changed

Update : I try flashing the TWRP recovery again, but now its freezing on the fastboot mode. Probably still installing. Hopefully everything went well and i can successfully install it.

Graiden05 said:
Did You know that to use fastboot tablet should be loaded in fastboot mode? If You connect it in fastboot mode and Windows shows no recognised fastboot or bootloader interface You need a proper driver.
Click to expand...
Click to collapse
After i run this command
fastboot -i 0x0b05 flash recovery TWRP.img
Click to expand...
Click to collapse
it freeze.(I have waiting for 30mins but still nothing significant comes up.)
There is three option to choose from (RCK, Android and WipeData)
Now under the "Device and Printer", there is a fastboot devices (unspecified). But when i see it in properties of this fastboot device, it's manufacturer is still under ClockworkMod. See attachment

Try this guide.

Help please.

Long time android user and "moder" here. Never owned an HTC device other than the ONE which I didn't have long. I just acquired this phone from some guy at my job who tried to mod it and he has it rooted with CM10 (which is ICS right? because it's ICS on it don't remember if it was 10 or not). I've downloaded, many, many roms over the past few days from JB to KK and tried to flash them and I successfully flash them in CWM but it just stays on the white HTC screen, and doesn't boot up. Any idea why this is happening?

C-4Nati said:
Long time android user and "moder" here. Never owned an HTC device other than the ONE which I didn't have long. I just acquired this phone from some guy at my job who tried to mod it and he has it rooted with CM10 (which is ICS right? because it's ICS on it don't remember if it was 10 or not). I've downloaded, many, many roms over the past few days from JB to KK and tried to flash them and I successfully flash them in CWM but it just stays on the white HTC screen, and doesn't boot up. Any idea why this is happening?
Click to expand...
Click to collapse
if you are on S-ON flash 4ext recovery
format all partitions except sdcard from 4ext
enable smartflash from 4ext
flash the rom
done

@C-4Nati also..if your bootloader is still s-on state (and stil using cwm recovery)..did you already flashing a boot.img from the rom that you had already installed..?
if not yet..you can try flashing it through fastboot.. "fastboot flash boot boot.img"

JJeamy said:
@C-4Nati also..if your bootloader is still s-on state (and stil using cwm recovery)..did you already flashing a boot.img from the rom that you had already installed..?
if not yet..you can try flashing it through fastboot.. "fastboot flash boot boot.img"
Click to expand...
Click to collapse
No he didn't flash a boot.IMG and its s on. No idea to do what you said :/ any guides you could link to

C-4Nati said:
No he didn't flash a boot.IMG and its s on. No idea to do what you said :/ any guides you could link to
Click to expand...
Click to collapse
If we know ur bootloader details then would make things easier, (turn off phone then press volume down + power) anyway, both these links will get u to where u want to be
http://forum.xda-developers.com/showthread.php?t=1864053
Or here. http://forum.xda-developers.com/showthread.php?t=1631861
Also as @rzr86 said, flash latest 4ext recovery (added below)

jmcclue said:
If we know ur bootloader details then would make things easier, (turn off phone then press volume down + power) anyway, both these links will get u to where u want to be
http://forum.xda-developers.com/showthread.php?t=1864053
Or here. http://forum.xda-developers.com/showthread.php?t=1631861
Also as @rzr86 said, flash latest 4ext recovery (added below)
Click to expand...
Click to collapse
This is it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

C-4Nati said:
This is it.
Click to expand...
Click to collapse
ok, have u fastboot setup on ur pc?

jmcclue said:
ok, have u fastboot setup on ur pc?
Click to expand...
Click to collapse
I'm not sure so I'm assuming that means no lol.

C-4Nati said:
I'm not sure so I'm assuming that means no lol.
Click to expand...
Click to collapse
click the first link i posted n set it up

jmcclue said:
click the first link i posted n set it up
Click to expand...
Click to collapse
I installed the sdk and fastboot and everything, and when I enter the fastboot oem token indentifier command all the command prompt says is waiting on device. I've double checked all instructions and it just keeps saying waiting on device.
Edit- I tried to flash the 4ext in cwm and it said installation aborted everytime.

C-4Nati said:
I installed the sdk and fastboot and everything, and when I enter the fastboot oem token indentifier command all the command prompt says is waiting on device. I've double checked all instructions and it just keeps saying waiting on device.
Edit- I tried to flash the 4ext in cwm and it said installation aborted everytime.
Click to expand...
Click to collapse
you are already unlocked your bootloader..so you don't need get identifier token again to unlock your bootloader..
1. first way..like what rzr86 and jmcclue said above..because you're still s-on but already had unlocked bootloader..they've suggest you to installing 4ext recovery for the next future you can easily installing of custom rom...because 4ext recovery is already option "SmartFlash" that fuction can installing custom rom with automatically supported also installing a boot.img from the rom itself under s-on devices like yours..
to installing that 4ext recovery...you can download recovery.zip from here.., then extracted that recovery.zip file to get recovery.img file...then copied recovery.img file to your sdk / adb folder (that are a same place as your adb.exe and fastboot.exe), after that...you can boot your phone to bootloader mode..then select "FASTBOOT" from there, then plug your phone to pc..until indicator in the phone has "FASTBOOT-USB", after that you can open cmd from your adb folder (just press and hold shift + right click on empty space from that folder and select "Open command window here") ...then typing command "fastboot devices" ..see if the output has detect your phone serial number.. if so...then continued typing "fastboot flash recovery recovery.img" then "fastboot reboot-bootloader" done..now you can tested it go to your 4ext recovery..and now you can enabled it "SmartFlash" from tools option before you installing any custom rom from 4ext recovery...
2. second way...if you don't want change you cwm recovery..you can fix your booting stuck by just flashing a boot.img extracted from the rom.zip itself with manual flashing from fastboot..
to do that...firstly just copied rom.zip that you wanna installing to another folder..then extracting / unzipping that file...then copied boot.img to your adb / sdk (same place as your adb.exe and fastboot.exe) folder..then after you've already installing that custom rom from cwm..you must reboot your phone to bootloader again (don't booting the rom first), then select FASTBOOT from there..then plug your phone to pc until indicator in your phone has FASTBOOT-USB..then open cmd from your adb / sdk folder..then typing command "fastboot flash boot boot.img" then "fastboot reboot" done...now you can see that the phone can booting of the rom normally or not..
hope this help..

JJeamy said:
you are already unlocked your bootloader..so you don't need get identifier token again to unlock your bootloader..
1. first way..like what rzr86 and jmcclue said above..because you're still s-on but already had unlocked bootloader..they've suggest you to installing 4ext recovery for the next future you can easily installing of custom rom...because 4ext recovery is already option "SmartFlash" that fuction can installing custom rom with automatically supported also installing a boot.img from the rom itself under s-on devices like yours..
to installing that 4ext recovery...you can download recovery.zip from here.., then extracted that recovery.zip file to get recovery.img file...then copied recovery.img file to your sdk / adb folder (that are a same place as your adb.exe and fastboot.exe), after that...you can boot your phone to bootloader mode..then select "FASTBOOT" from there, then plug your phone to pc..until indicator in the phone has "FASTBOOT-USB", after that you can open cmd from your adb folder (just press and hold shift + right click on empty space from that folder and select "Open command window here") ...then typing command "fastboot devices" ..see if the output has detect your phone serial number.. if so...then continued typing "fastboot flash recovery recovery.img" then "fastboot reboot-bootloader" done..now you can tested it go to your 4ext recovery..and now you can enabled it "SmartFlash" from tools option before you installing any custom rom from 4ext recovery...
2. second way...if you don't want change you cwm recovery..you can fix your booting stuck by just flashing a boot.img extracted from the rom.zip itself with manual flashing from fastboot..
to do that...firstly just copied rom.zip that you wanna installing to another folder..then extracting / unzipping that file...then copied boot.img to your adb / sdk (same place as your adb.exe and fastboot.exe) folder..then after you've already installing that custom rom from cwm..you must reboot your phone to bootloader again (don't booting the rom first), then select FASTBOOT from there..then plug your phone to pc until indicator in your phone has FASTBOOT-USB..then open cmd from your adb / sdk folder..then typing command "fastboot flash boot boot.img" then "fastboot reboot" done...now you can see that the phone can booting of the rom normally or not..
hope this help..
Click to expand...
Click to collapse
Hey, I really really appreciate you trying to help. Both those directions are clear and I know I could easily do either but the only problem is for some reason my computer doesn't recognize the phone and when in fastboot mode it never says fastboot-usb and cmd always says waiting on device. I know usb debugging is enabled but I'm on an aosp rom so I didn't have the option to uncheck fastboot under power, is that the problem maybe? I have android SDK installed and the app "htc sync" so I'm not sure why it doesn't recognize the phone.
edit -it did end up saying "fastboot usb" but in cmd it still said waiting on device and when I typed fastboot devices no serial number came up.

C-4Nati said:
Hey, I really really appreciate you trying to help. Both those directions are clear and I know I could easily do either but the only problem is for some reason my computer doesn't recognize the phone and when in fastboot mode it never says fastboot-usb and cmd always says waiting on device. I know usb debugging is enabled but I'm on an aosp rom so I didn't have the option to uncheck fastboot under power, is that the problem maybe? I have android SDK installed and the app "htc sync" so I'm not sure why it doesn't recognize the phone.
Click to expand...
Click to collapse
what OS you have on your computer?

Mile_zdr said:
what OS you have on your computer?
Click to expand...
Click to collapse
Let me edit my previous post, as in the bootloader it did end up saying "fastboot usb" but in cmd it still said waiting on device and when I typed fastboot devices no serial number came up. I have windows 8.1

C-4Nati said:
Let me edit my previous post, as in the bootloader it did end up saying "fastboot usb" but in cmd it still said waiting on device and when I typed fastboot devices no serial number came up. I have windows 8.1
Click to expand...
Click to collapse
Could this have something to do with it? For some reason the device is recognized if I go into device and printers but it's not listed under the "this PC" area like all my other devices go to. It also wont let me browse the phones internal storage for some reason. http://i.imgur.com/FnhjwYa.png
edit - this is what it says while I'm in fastboot mode and plug the phone in.

C-4Nati said:
Could this have something to do with it? For some reason the device is recognized if I go into device and printers but it's not listed under the "this PC" area like all my other devices go to. It also wont let me browse the phones internal storage for some reason. http://i.imgur.com/FnhjwYa.png
edit - this is what it says while I'm in fastboot mode and plug the phone in.
Click to expand...
Click to collapse
i lot of people have problems with fasboot and win 8.1 i don't know does have solution, but try with win 7 if you have another computer

Mile_zdr said:
i lot of people have problems with fasboot and win 8.1 i don't know does have solution, but try with win 7 if you have another computer
Click to expand...
Click to collapse
I used my windows 7 pc and everything worked. You guys are all AWESOME! and I appreciate all the help. Now I'm having problems with getting signal lol -.- I purchased an unlock code from a website and when I put my t mobile sim it and the phone boots it says enter code and I do and it says network unlock successful but I won't get signal at all. I've rebooted and entered code again and taken sim out and put back in to no avail lol. This phone just won't be easy lol.

C-4Nati said:
I used my windows 7 pc and everything worked. You guys are all AWESOME! and I appreciate all the help. Now I'm having problems with getting signal lol -.- I purchased an unlock code from a website and when I put my t mobile sim it and the phone boots it says enter code and I do and it says network unlock successful but I won't get signal at all. I've rebooted and entered code again and taken sim out and put back in to no avail lol. This phone just won't be easy lol.
Click to expand...
Click to collapse
dial *#*#4636#*#* than go to phone information and set the network to WCDMA prefered see if it work

Mile_zdr said:
dial *#*#4636#*#* than go to phone information and set the network to WCDMA prefered see if it work
Click to expand...
Click to collapse
I did that an it didn't do anything. This is originally a T-Mobile phone but a local company called Cincinnati Bell (which is also a GSM/sim card using company) buys units to resell and locks them on their service. I have T-Mobile and paid for the unlock code so I could use T-Mobile on it but so far it's not working (though it says network unlock successful).

C-4Nati said:
I did that an it didn't do anything. This is originally a T-Mobile phone but a local company called Cincinnati Bell (which is also a GSM/sim card using company) buys units to resell and locks them on their service. I have T-Mobile and paid for the unlock code so I could use T-Mobile on it but so far it's not working (though it says network unlock successful).
Click to expand...
Click to collapse
?
I don't know what to tell you... :/ do you have another sim card from other carrier just to see everything work's okey?

[Q] Bootloop - no recovery - no system - reset tamper flag - RMA

Hi guys,
my N5 is broken and i want to RMA ... It bootloops at the Google Logo, I can enter Fastboot, but NOT the recovery.
I managed to flash stock via fastboot and I locked the Bootloader.
After that I tried to reset the Tamper Flag with osm0sis' BootUnlocker zip ... well, ya need recovery for that. I tried to boot twrp with
Code:
fastboot boot recovery
but that returns "cannot load 'recovery': No such file or directory".
flashing the recovery works well ... but it doesn't boot into recovery, its bootlooping here to, even if you select recovery mode in fastboot.
So, any ideas how to do that now ?
thanks in advance !
EDIT
AWWW ..... after re-reading my post, I realized the command was wrong ..... its just boot ... not boot recovery ....jeeez
But anyway, even that results in a Bootloop .... so no way to access anything else but fastboot.

momsi said:
Hi guys,
my N5 is broken and i want to RMA ... It bootloops at the Google Logo, I can enter Fastboot, but NOT the recovery.
I managed to flash stock via fastboot and I locked the Bootloader.
After that I tried to reset the Tamper Flag with osm0sis' BootUnlocker zip ... well, ya need recovery for that. I tried to boot twrp with
Code:
fastboot boot recovery
but that returns "cannot load 'recovery': No such file or directory".
flashing the recovery works well ... but it doesn't boot into recovery, its bootlooping here to, even if you select recovery mode in fastboot.
So, any ideas how to do that now ?
thanks in advance !
Click to expand...
Click to collapse
it wont boot into recovery. boot into bootloader, then recovery, if no recovery, flash a recovery. btw, dont boot a recovery, flash it. if you run the script to boot it, itll only boot once. you need to fastboot flash recovery recoveryname.img
edit.. i noticed that you are booting a recovery. booting it only works for a one time use. dont boot it, flash it.
fastboot flash recovery recoveryname.img
Click to expand...
Click to collapse

fastboot boot recovery boots the phone to a recovery image on your PC.
So like fastboot flash...
fastboot boot path\to\recovery.img
Sent from my Nexus 5 using Tapatalk

I know that booting it is only one time use, I did that on purpose. But it didn't work either, see edit in OP.

momsi said:
I know that booting it is only one time use, I did that on purpose. But it didn't work either, see edit in OP.
Click to expand...
Click to collapse
the boot command is wrong as well. its fastboot boot recovery recoveryname.img
and the recovery file has to be in the same folder on your desktop as fastboot.

simms22 said:
the boot command is wrong as well. its fastboot boot recovery recoveryname.img
and the recovery file has to be in the same folder on your desktop as fastboot.
Click to expand...
Click to collapse
fastboot boot doesn't need you to identify a NAND partition as you're loading it into memory.
fastboot boot recovery.img is the command if your recovery is called recovery.img
The recovery file can be in any directory.
If you haven't installed fastboot correctly, you need to open the command prompt in (or change directory TO) the directory where fastboot.exe is. The easiest way to deal with this is as you say, drop the recovery image there, but you can also just prefix the recovery.img with the path if its anywhere else
However best practice would be to install fastboot correctly by manually adding it to environment variables or using the 15 second installer (or even dropping fastboot.exe in an existing environment variable path such as c:\windows\system32) at which point you can run fastboot no matter what directory command prompt is running in.
I cover most of the above in my "adb and fastboot. What is it?" Sticky thread in my signature
Anyway, sorry OP, I think you're stuck.
Sent from my Nexus 5 using Tapatalk

rootSU said:
fastboot boot doesn't need you to identify a NAND partition as you're loading it into memory.
fastboot boot recovery.img is the command if your recovery is called recovery.img
The recovery file can be in any directory.
If you haven't installed fastboot correctly, you need to open the command prompt in (or change directory TO) the directory where fastboot.exe is. The easiest way to deal with this is as you say, drop the recovery image there, but you can also just prefix the recovery.img with the path if its anywhere else
However best practice would be to install fastboot correctly by manually adding it to environment variables or using the 15 second installer (or even dropping fastboot.exe in an existing environment variable path such as c:\windows\system32) at which point you can run fastboot no matter what directory command prompt is running in.
I cover most of the above in my "adb and fastboot. What is it?" Sticky thread in my signature
Anyway, sorry OP, I think you're stuck.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
hmm.. ive always used fastboot boot recovery recoveryname.img, and never an issue.

simms22 said:
hmm.. ive always used fastboot boot recovery recoveryname.img, and never an issue.
Click to expand...
Click to collapse
Are you sure? It *shouldn't* work and certainly doesn't for me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

rootSU said:
Are you sure? It *shouldn't* work and certainly doesn't for me.
Click to expand...
Click to collapse
you are right

Ah ok
Sent from my Nexus 5 using Tapatalk

Try fastboot format recovery then flash it again.
Sent from my Nexus 5 using XDA Free mobile app

Atomix86 said:
Try fastboot format recovery then flash it again.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
did that ... didn't work....

Didn't work as in the format failed, or the recovery flash failed?
Sent from my Nexus 5 using XDA Free mobile app

I didn't see it mentioned but, have you tried a different alternative recovery? I speak from experience at one point after rooting, my phone would not launch the stock recovery. I then tried to use CWM (it's what I was familiar with) and it wouldn't boot either. I then went to TWRP and it did work.
Is it maybe possible the recovery image you have is corrupted or incomplete? Possible maybe you have the wrong one you're trying to flash and boot? I once mistakenly flashed my tablet with the recovery for my phone. Fixed that issue but it drove me nuts for a few hours wondering why it wasn't working.

Didnt work as in it stuck in the same bootloop again ...
no luck with other recoverys or other ..tried several
i only can enter fastboot

[Q] I guess I messed up pretty bad.

Hey there. I hate to bother everyone, i really do, but after searching countless forums, and trying infinite solutions, i'm at a loss of what to do. I want to flash to stock rom, I'm on paranoid android at the moment. Now normally this wouldn't be an issue- but somehow, someway, my bootloader is locked, and i cannot get it to unlock again at all. i've tried doing it with the OPO tool, tried through cmd, nothing. all that happens upon running fastboot oem unlock is my device boots into recovery (philz). i have no idea what to do, but it's really bumming me out. My model is the 64gb one.
also as a side problem, i originally tried flashing THIS ROM, and ever since then my fastboot is in the chinese version. I couldn't flash to stock before hand because it kept telling me my fastboot was outdated. how can i fix this as well?
i really, really, REALLY appreciate any help i can get. i always surf for hours on forums trying to resolve the problem myself before making a new thread, but i have no other options now.

You did mess up pretty bad (by posting in the wrong section).
Does the command prompt give you any error when you try to unlock the bootloader?
Try reading through this thread, it may help (read all of it before you attempt anything)
http://forum.xda-developers.com/oneplus-one/help/oneplus-one-unable-to-unlock-bootloader-t2845626

sahil04 said:
You did mess up pretty bad (by posting in the wrong section).
Does the command prompt give you any error when you try to unlock the bootloader?
Click to expand...
Click to collapse
my sincerest apologies. i haven't actually used XDA in a while. give me a little bit though, upon trying again, apparently my abd isn't working right and isn't recognized as an internal command.
update: those threads always result in telling me to do this which is what i'm trying to do right now, though i've tried before and still tend to get a straight boot into recovery.

Sounds like you are not in the correct directory to run adb.
Try this:
cd (location of adb.exe)
example:
cd C:\android\platform-tools\
Then try to run this command with your device plugged in:
adb.exe devices

sahil04 said:
Sounds like you are not in the correct directory to run adb.
Try this:
cd (location of adb.exe)
example:
cd C:\android\platform-tools\
Then try to run this command with your device plugged in:
adb.exe devices
Click to expand...
Click to collapse
i'm in the right directory. i'm following this guide and i'm at the part where it tells me to type "fastboot oem unlock" it then tells me to do a fastboot reboot after that script finishes running which is where the problem comes in. the phone reboots into recovery IMMEDIATELY after inputting the oem unlock command, not giving me the chance to do anything else.

dokibot said:
i'm in the right directory. i'm following this guide and i'm at the part where it tells me to type "fastboot oem unlock" it then tells me to do a fastboot reboot after that script finishes running which is where the problem comes in. the phone reboots into recovery IMMEDIATELY after inputting the oem unlock command, not giving me the chance to do anything else.
Click to expand...
Click to collapse
try sideloading... Adb sideload "name of rom".zip
Sent from my A0001 using XDA Premium 4 mobile app

sahil04 said:
You did mess up pretty bad (by posting in the wrong section).
Does the command prompt give you any error when you try to unlock the bootloader?
Try reading through this thread, it may help (read all of it before you attempt anything)
http://forum.xda-developers.com/oneplus-one/help/oneplus-one-unable-to-unlock-bootloader-t2845626
Click to expand...
Click to collapse
this is what the cmd shows when i run oem unlock. then the phone just boots into recovery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Setting.Out said:
try sideloading... Adb sideload "name of rom".zip
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i've never side loaded before? i can't find anything specific for the opo
edit: all i can find is how to flash roms with it, when i really wanna get my bootloader unlocked

dokibot said:
i've never side loaded before? i can't find anything specific for the opo
edit: all i can find is how to flash roms with it, when i really wanna get my bootloader unlocked
Click to expand...
Click to collapse
Try the following links:
Link1
Link2

KDurantula said:
Try the following links:
Link1
Link2
Click to expand...
Click to collapse
surely there's something other than using a ubuntu virtual box? i don't have a lot of disk space right now, and i'd much rather have some other solution. anything else.

dokibot said:
surely there's something other than using a ubuntu virtual box? i don't have a lot of disk space right now, and i'd much rather have some other solution. anything else.
Click to expand...
Click to collapse
I was kind of in the same situation as you, nothing else would work for me lol. If all else fails, give it a shot!

Go back to stock and start over, please see this guide to go back to stock:
Download the official CM11S from cyanogen website http://builds.cyngn.com/factory/bacon/cm-11.0-XNPH33R-bacon-signed-fastboot.zip and follow this guide:
First time flashing CyanogenMod 11S on your device, or coming from another ROM (e.g. ColorOS)?
WARNING: This procedure will factory reset your device! Accounts, applications, settings, everything will be lost! This is really a factory reset.
Download the file cm-11.0-XNPH33R-bacon-signed-fastboot.zip to your PC from the link above
Reboot your device into Fastboot mode by holding PWR+VOL-UP
Connect your device via USB to your PC
Unpack the downloaded zip
Open a command prompt (Windows) or terminal (Linux/Mac) and perform the following fastboot commands:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot update -w cm-11.0-XNPH33R-bacon-signed-fastboot.zip (file used to extract the files above)
This will make you device go back to stock, check if it works now.
Hope this helps.

i can't flash anything. my bootloader isn't unlocked. this is my problem.

dokibot said:
i can't flash anything. my bootloader isn't unlocked. this is my problem.
Click to expand...
Click to collapse
Do you have a custom recovery? If you do, your bootloader is unlocked.
Just sideload a XNPH38R.zip, Calkulin's one, or the official. Then try to use fastboot once more.
My guess is that this fixes your problem and that fastboot will work again.
P.S. Even if you haven't been on XDA for a while how in God's name would you post in "Original Android Development"...?

TiVON said:
Do you have a custom recovery? If you do, your bootloader is unlocked.
Just sideload a XNPH38R.zip, Calkulin's one, or the official. Then try to use fastboot once more.
My guess is that this fixes your problem and that fastboot will work again.
P.S. Even if you haven't been on XDA for a while how in God's name would you post in "Original Android Development"...?
Click to expand...
Click to collapse
**** i didn't even realize i was in original. my bad wow. Yeah i have philz right now. do i need to wipe everything to do this. i'm scared of wiping because if i do, since i can't flash anything, i'll be stuck without a rom at all. i'm downloading the official zip, and i'm about to try sideloading it.
edit: sideload failed. might be because i didn't wipe. error in /tmp/update.zip (status 7). it suggested i do a factory reset, tried that, still same error.

dokibot said:
**** i didn't even realize i was in original. my bad wow. Yeah i have philz right now. do i need to wipe everything to do this. i'm scared of wiping because if i do, since i can't flash anything, i'll be stuck without a rom at all. i'm downloading the official zip, and i'm about to try sideloading it.
edit: sideload failed. might be because i didn't wipe. error in /tmp/update.zip (status 7). it suggested i do a factory reset, tried that, still same error.
Click to expand...
Click to collapse
Have you tried flashing the stock rom with the stock recovery through the custom recovery and then trying to re-unlock the bootloader?

sahil04 said:
Have you tried flashing the stock rom with the stock recovery through the custom recovery and then trying to re-unlock the bootloader?
Click to expand...
Click to collapse
i can't flash stock. it tells me the bootloader is locked, and stops the process.

hugoprh said:
Go back to stock and start over, please see this guide to go back to stock:
Download the official CM11S from cyanogen website http://builds.cyngn.com/factory/bacon/cm-11.0-XNPH33R-bacon-signed-fastboot.zip and follow this guide:
First time flashing CyanogenMod 11S on your device, or coming from another ROM (e.g. ColorOS)?
WARNING: This procedure will factory reset your device! Accounts, applications, settings, everything will be lost! This is really a factory reset.
Download the file cm-11.0-XNPH33R-bacon-signed-fastboot.zip to your PC from the link above
Reboot your device into Fastboot mode by holding PWR+VOL-UP
Connect your device via USB to your PC
Unpack the downloaded zip
Open a command prompt (Windows) or terminal (Linux/Mac) and perform the following fastboot commands:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot update -w cm-11.0-XNPH33R-bacon-signed-fastboot.zip (file used to extract the files above)
This will make you device go back to stock, check if it works now.
Hope this helps.
Click to expand...
Click to collapse
none of this works. cant even get it to open NON-HLOS.bin everytime i try it just gives me "error: cannot open "NON-HLOS.bin'" i have my path set to
cd desktop/sdk/platform-tools/(folder i named with all the zip files)
is that right?

dokibot said:
none of this works. cant even get it to open NON-HLOS.bin everytime i try it just gives me "error: cannot open "NON-HLOS.bin'" i have my path set to
cd desktop/sdk/platform-tools/(folder i named with all the zip files)
is that right?
Click to expand...
Click to collapse
Try this:
cd C:\Users\(username)\Desktop\SDK\platform-tools\
Also, did you extract the files out of the zip file?

dokibot said:
none of this works. cant even get it to open NON-HLOS.bin everytime i try it just gives me "error: cannot open "NON-HLOS.bin'" i have my path set to
cd desktop/sdk/platform-tools/(folder i named with all the zip files)
is that right?
Click to expand...
Click to collapse
Install this http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
So you can get the adb and fastboot from anywhere on the command line, then open the command prompt and navigate to that folder and copy line by line from the above tutorial.
The last line will require the original ZIP file to be in the same folder has the extracted files.
Hope this helps.

[Q] Stock OPO soft bricked after turning off at night.

Okay, here's the deal... I have an OPO (not mine) that is completely stock running, I would presume 5.0.2. I'm not exactly sure which build. But I was told that she turned the phone off at night and charged it. Turned it on in the morning and it got stuck on the cyanogen logo. No boot loops, no getting past that. Just sitting there. The device is stock, bootloader locked, no root. I also highly doubt that ADB debugging was turned on while it was working...
I'm trying to wipe it bring it back to stock, but I'm not having any success. I've gone in to Cyanogen recovery and wipe/factory reset, wipe cache, wipe media. Reboot, still stuck. When I click apply update in recovery, it gives me a bunch of errors saying so and so directory isn't found. So that leaves to me to believe that something went bad.
I just tried to fastboot oem unlock, said it finished in a few seconds. Then I tried to fastboot the factory image files and after the first one (modem), it gave me an error saying the bootloader is locked.
I'm out of ideas and the unbrick a hard bricked OPO thread said it wouldn't work, so I haven't tried it. Any advice on where to look would be much appreciated.

Anybody?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I get this when I hit Apply Update and then use storage as option.

moobieboobie said:
Anybody?
I get this when I hit Apply Update and then use storage as option.
Click to expand...
Click to collapse
Flash The whole Rom with fastboot to fix The Problem ....make a backup of your internal sdcard....

jamal2367 said:
Flash The whole Rom with fastboot to fix The Problem ....make a backup of your internal sdcard....
Click to expand...
Click to collapse
That's the problem. I can't because the bootloader is locked. When I try to unlock it, it runs the command. Then when I try to fastboot flash, it tells me the bootloader is locked. I have my own OPO that I have unlocked and rooted, so knowing how to unlock isn't an issue either.

moobieboobie said:
That's the problem. I can't because the bootloader is locked. When I try to unlock it, it runs the command. Then when I try to fastboot flash, it tells me the bootloader is locked. I have my own OPO that I have unlocked and rooted, so knowing how to unlock isn't an issue either.
Click to expand...
Click to collapse
Run CMD as Admin ...have you install the right driver for your phone and install the ADB drivers correctly? ...

jamal2367 said:
Run CMD as Admin ...have you install the right driver for your phone and install the ADB drivers correctly? ...
Click to expand...
Click to collapse
Yes, all updated drivers. Drivers are not the issue since I can execute commands while in fastboot. The issue is not having an unlocked bootloader, so I can't flash anything and it won't unlock bootloader.

moobieboobie said:
Yes, all updated drivers. Drivers are not the issue since I can execute commands while in fastboot. The issue is not having an unlocked bootloader, so I can't flash anything and it won't unlock bootloader.
Click to expand...
Click to collapse
Ps did phone was encrypt?

geowolf1000 said:
Ps did phone was encrypt?
Click to expand...
Click to collapse
No, phone was not encrypted and ColorOS unbrick didn't work. It recognizes the phone, I hit start and it does it's thing. After first green bar, it boot loops instead of flashing all the files. Ran as admin and all the drivers are good.

moobieboobie said:
No, phone was not encrypted and ColorOS unbrick didn't work. It recognizes the phone, I hit start and it does it's thing. After first green bar, it boot loops instead of flashing all the files. Ran as admin and all the drivers are good.
Click to expand...
Click to collapse
hit install from recovery
Choose file to update
Search files
Do you see your partition?
System exist?
What system do you have color or cyanogen?
Data?
Sd?

geowolf1000 said:
hit install from recovery
Choose file to update
Search files
Do you see your partition?
System exist?
What system do you have color or cyanogen?
Data?
Sd?
Click to expand...
Click to collapse
See post above with picture. It was running stock Cyanogen OS 12, not modded or anything. When I hit Apply Update and Choose from internal storage, I get the error in above picture.

moobieboobie said:
See post above with picture. It was running stock Cyanogen OS 12, not modded or anything. When I hit Apply Update and Choose from internal storage, I get the error in above picture.
Click to expand...
Click to collapse
But you have adb
Sideload full rom included recovery
From adb

geowolf1000 said:
But you have adb
Sideload full rom included recovery
From adb
Click to expand...
Click to collapse
If by sideload, you mean copy the rom to device and then load..I can not access device storage. ADB sideload rom through command line gives me the same errors you see in the above picture.

moobieboobie said:
If by sideload, you mean copy the rom to device and then load..I can not access device storage. ADB sideload rom through command line gives me the same errors you see in the above picture.
Click to expand...
Click to collapse
F**ing recovery
With adb you can navigate to system and change built.prompt and enable debugg mode
All the other method i know need root so dd (replace)recovery from adb

geowolf1000 said:
F**ing recovery
With adb you can navigate to system and change built.prompt and enable debugg mode
All the other method i know need root so dd (replace)recovery from adb
Click to expand...
Click to collapse
Can you give instructions on how to? I'm not too familiar with adb, but can follow steps.

moobieboobie said:
Can you give instructions on how to? I'm not too familiar with adb, but can follow steps.
Click to expand...
Click to collapse
Even this suggest need root.
All need root.... To system...

moobieboobie said:
Can you give instructions on how to? I'm not too familiar with adb, but can follow steps.
Click to expand...
Click to collapse
Another trick for installation is
Code:
fastboot boot <path/name of the recovery twrp img>
It will boot your phone into recovery once from the recovery image
stored in your PC temporarily
then you can flash the zip either by sideload or
Check this

geowolf1000 said:
Another trick for installation is
Code:
fastboot boot <path/name of the recovery twrp img>
It will boot your phone into recovery once from the recovery image
stored in your PC temporarily
then you can flash the zip either by sideload or
Check this
Click to expand...
Click to collapse
cannot fastboot boot recovery, tells me bootloader is locked and fails. the link requires unlocking bootloader, which is not working for me.

moobieboobie said:
cannot fastboot boot recovery, tells me bootloader is locked and fails. the link requires unlocking bootloader, which is not working for me.
Click to expand...
Click to collapse
Haz a parametre here

There is a way to flash an unlocked bootloader if you can't fastboot oem unlock.
As you already tried the color.zip method you should already have most of the needed files.
Download the attachment and unzip it into color folder replacing the files emmc_appsboot.mbn and rawprogram0_64.xml (backup the originals first).
-power off the OPO
-hold VolUp and plug into PC
-on PC open device manager, OPO should be in QDloader 9008
-keep an eye on device manager and start msm8974downloadtool from color.zip
-when in device manager the QDloader 9008 disconnects press stop in msm8974downloadtool
-OPO should now be Qualcomm Diagnostics 9006 in device manager
-download MiFlash from here http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable/ and set it up like on the pictures on that website
-click refresh. now it should show you OPO on the respective COM port. click flash
-when successfull finished unplug and press and hold power for 30 seconds
-now start into fastboot with power + VolUp and there is your unlocked bootloader
-now you can flash cos with fastboot
The rawprogram0_64xml is edited so that it only writes partition table and flashes sbl1, dbi, rpm, tz, recovery and emmc_appsboot.
This worked for me when i couldn't flash with msm8974downloadtool, it always flashed modem, started with flashing system and then began from the start again.

tropenfrucht said:
There is a way to flash an unlocked bootloader if you can't fastboot oem unlock.
As you already tried the color.zip method you should already have most of the needed files.
Download the attachment and unzip it into color folder replacing the files emmc_appsboot.mbn and rawprogram0_64.xml (backup the originals first).
-power off the OPO
-hold VolUp and plug into PC
-on PC open device manager, OPO should be in QDloader 9008
-keep an eye on device manager and start msm8974downloadtool from color.zip
-when in device manager the QDloader 9008 disconnects press stop in msm8974downloadtool
-OPO should now be Qualcomm Diagnostics 9006 in device manager
-download MiFlash from here http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable/ and set it up like on the pictures on that website
-click refresh. now it should show you OPO on the respective COM port. click flash
-when successfull finished unplug and press and hold power for 30 seconds
-now start into fastboot with power + VolUp and there is your unlocked bootloader
-now you can flash cos with fastboot
The rawprogram0_64xml is edited so that it only writes partition table and flashes sbl1, dbi, rpm, tz, recovery and emmc_appsboot.
This worked for me when i couldn't flash with msm8974downloadtool, it always flashed modem, started with flashing system and then began from the start again.
Click to expand...
Click to collapse
gave it a shot a few minutes ago.. As soon as 9008 dc fom device manager, i hit stop. the phone turns off or reboots (the screen goes blank)... I hear the connection, but no 9006.