Database Info

[Q] Please help me, White screen -frozen

Hello, I have HTC Desire S, my phone was rooted i flashed it rocovery.img and then i booted my phone in CWM - touch i was so happy when i saw that, I clicked install rom from sdcard i installed MikRunny, my phone restarted and stays on white screen(htc) wont turn on. my bootloader is unlocked via htcDec, S-ON. can anyone help me? sorry for my English.

Try using adb reboot recovery
Sent from my HTC Desire S using XDA

http://forum.xda-developers.com/showthread.php?t=1544670
R.

B-GeeK [AL] - [MKD] said:
Hello, I have HTC Desire S, my phone was rooted i flashed it rocovery.img and then i booted my phone in CWM - touch i was so happy when i saw that, I clicked install rom from sdcard i installed MikRunny, my phone restarted and stays on white screen(htc) wont turn on. my bootloader is unlocked via htcDec, S-ON. can anyone help me? sorry for my English.
Click to expand...
Click to collapse
Errr...this may sound a little patronizing, but you need to flash boot.img (extract it from the mikrunny zip file) manually using fastboot.
For further details, use search.

B-GeeK [AL] - [MKD] said:
Hello, I have HTC Desire S, my phone was rooted i flashed it rocovery.img and then i booted my phone in CWM - touch i was so happy when i saw that, I clicked install rom from sdcard i installed MikRunny, my phone restarted and stays on white screen(htc) wont turn on. my bootloader is unlocked via htcDec, S-ON. can anyone help me? sorry for my English.
Click to expand...
Click to collapse
And once more, we should have stayed with xtc and revolutionary to unlock. Thx htc nice attempt, but next time pls unlock everything or leave it be (or at last state the additional needs at the form maybe there a bit more users read it), at least for those devices that already got unlock methods.
Swyped from my Desire S far away from my PC (maybe)

Tectas said:
And once more, we should have stayed with xtc and revolutionary to unlock. Thx htc nice attempt, but next time pls unlock everything or leave it be (or at last state the additional needs at the form maybe there a bit more users read it), at least for those devices that already got unlock methods.
Swyped from my Desire S far away from my PC (maybe)
Click to expand...
Click to collapse
They would have... Except that some idiot came up with a new and unsupported hboot...and a monster was born... The HTCDevil unlock ....
Beamed from the Dark Side using xda premium.

enigmaamit said:
Errr...this may sound a little patronizing, but you need to flash boot.img (extract it from the mikrunny zip file) manually using fastboot.
For further details, use search.
Click to expand...
Click to collapse
Is this file that i need to flash? and do i need to rename image to recovery? if you can tell me in more details ill be very thankfull,(sorry for my english)
{
"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"
}

B-GeeK [AL] - [MKD] said:
Is this file that i need to flash? and do i need to rename image to recovery? if you can tell me in more details ill be very thankfull,(sorry for my english)
Click to expand...
Click to collapse
You need to extract boot.img from the mikrunny.zip file and place it in your android tools folder (where you have your adb and fastboot batch files)
Then boot into fastboot on your phone, and after making sure your device is detected... type the following command;
fastboot flash boot boot.img
no need to rename anything.
To read about fastboot and adb setup in detail, click on the link under Helpful Links in my signature.
You need to flash the specific boot.img extracted from each particular ROM every time you flash a new ROM in the future.
P.S : I can't see the attachment you posted... maybe you need to reupload it.

enigmaamit said:
They would have... Except that some idiot came up with a new and unsupported hboot...and a monster was born... The HTCDevil unlock ....
Beamed from the Dark Side using xda premium.
Click to expand...
Click to collapse
I know your right, but pls let me moan a little, it's really getting annoying^^
Swyped from my Desire S far away from my PC (maybe)

Tectas said:
I know your right, but pls let me moan a little, it's really getting annoying^^
Swyped from my Desire S far away from my PC (maybe)
Click to expand...
Click to collapse
Moan away then, my brother-in-agony! My fingers ache too trying to explain fastboot flash boot boot.img!!!

enigmaamit said:
You need to extract boot.img from the mikrunny.zip file and place it in your android tools folder (where you have your adb and fastboot batch files)
Then boot into fastboot on your phone, and after making sure your device is detected... type the following command;
fastboot flash boot boot.img
no need to rename anything.
To read about fastboot and adb setup in detail, click on the link under Helpful Links in my signature.
You need to flash the specific boot.img extracted from each particular ROM every time you flash a new ROM in the future.
P.S : I can't see the attachment you posted... maybe you need to reupload it.
Click to expand...
Click to collapse
this is http://imageshack.us/photo/my-images/29/mikrunny.jpg/

B-GeeK [AL] - [MKD] said:
this is http://imageshack.us/photo/my-images/29/mikrunny.jpg/
Click to expand...
Click to collapse
Yes, that's the one!

There is a perfect guide [Guide] How to root, install EXT4 recovery and custom ROM on HBOOT 2.00.0002, but it is not in the Index yet. I suggested to the author to inform ben_pyett, but he did not for some reason. I will post the link in the Index thread

amidabuddha said:
There is a perfect guide [Guide] How to root, install EXT4 recovery and custom ROM on HBOOT 2.00.0002, but it is not in the Index yet. I suggested to the author to inform ben_pyett, but he did not for some reason. I will post the link in the Index thread
Click to expand...
Click to collapse
Not near PC this evening, so please remind me by posting in index thread or pm
Add well as adding to index I'll also attempt to get this guide made into a sticky, as the constant new posts by HTCdev users suffering boot loops is unfortunately getting a little tedious.....it's just like back in the early days of revolutionary release
Swyped from my Desire S using XDA Premium

Unable to flash nightly AOKP 4.2.2

Hello,
I have been running the Milestone1 rom for AOKP for a while now. Everything is running dandy. I wanted to try out the nightly builds, specifically the aokp_evita_ unofficial_2013-07-08.zip
I have the bootloader unlocked as well as s-off
When i try to install that rom, it always ends up failed.
This what I see in TWRP 2.6.0.0
Updating partitions details...
running boot script..
Finished running boot script.
installing '/sdcard/aokp_evita_unofficial_2013-0708.zip'...
checking for MD5 file...
skipping MD5 check: no MD5 file found
assert failed: getprop("ro.bootloader") == "2.14.00"
E:Error executing updater binary in zip '/sdcard/aokp_evita_unofficial_2
Error flashing zip '/sdcard/aokp_evita_unofficial_2013-07-08.zip'
Updating partition details
Click to expand...
Click to collapse
I have h-boot 1.11.0000
I'm completely lost.
any help would be greatly appreciated.
Thanks

You need to upgrade to the 3.18 ruu. Since you're S-Off you should be good to go, just run it and flash AOKP.

RollTribe said:
You need to upgrade to the 3.18 ruu. Since you're S-Off you should be good to go, just run it and flash AOKP.
Click to expand...
Click to collapse
Im on a rogers one x. How and where can i get 3.18 RUU?

buhbuh said:
Im on a rogers one x. How and where can i get 3.18 RUU?
Click to expand...
Click to collapse
Download and run this RUU: (Do not relock bootloader, it is not needed with S-OFF)
http://bugsylawson.com/files/file/2...s320928l-101033224l-release-268972-signedexe/
Then you can either check for updates within your stock rom right after or download and install This OTA through the stock recovery which you can download here:
http://fotadl.htc.com/OTA_EVITA_UL_...128.32.34a_release_299850qstr7rxdbfuofl6j.zip
I would imagine you know how to check for the OTA on your phone.
But if you plan to download the OTA and flash it manually, you will want to copy The OTA zip file to your SD card.
Boot to your bootloader then select recovery.
When you get an image on your screen press and hold volume up and then press power. You will see a message that SD card could not be mounted. This is normal.
Then you will be in Stock recovery.
Select install update from Phone storage could also be called internal storage (do not select from SD card as it will be looking for an external card and not the internal memory and it will say it could not be mounted.)
Select the OTA zip file and it will start doing stuff.
Then when done, select reboot phone and it will install the rest of the OTA and voila you will be on 2.14 hboot.
Then you can reflash twrp 2.6 and then flash your rom and smile, maybe even frolic in the streets as a result of your accomplishments.
STOP THE PRESSES! milestone1 isn't even using the 3.4 kernel......... why would op need 2.14 hboot?
*edit* Nevermind I'm an idiot. Unofficial. Follow my directions or Flash the OFFICIAL rom if you don't want to go through all that hassle.

@exad he WAS running MS and is trying to flash nightly. That's the error he got in the OP.

RollTribe said:
@exad he WAS running MS and is trying to flash nightly. That's the error he got in the OP.
Click to expand...
Click to collapse
Yeah I see it now -_- Sorry!!!
My bad everyone! My bad! As you were! Carry on and all that.

OP... You can also run this http://dl3.htc.com/application/RUU_..._10.130.32.34_release_signed_With_Partial.exe ruu, this is the AT&T one. Options are good .

buhbuh said:
Im on a rogers one x. How and where can i get 3.18 RUU?
Click to expand...
Click to collapse
exad said:
Download and run this RUU: (Do not relock bootloader, it is not needed with S-OFF)
http://bugsylawson.com/files/file/2...s320928l-101033224l-release-268972-signedexe/
[/COLOR]
Click to expand...
Click to collapse
so should just download and run this RUU and then install try to install the nightly rom?
sorry for the many questions. This area is completely new to to me.

buhbuh said:
so should just download and run this RUU and then install try to install the nightly rom?
sorry for the many questions. This area is completely new to to me.
Click to expand...
Click to collapse
Yes you should follow my directions above. Sorry for confusing you
After the RUU you have to do the OTA portion too or you won't update to 3.18 or 3.17 or whatever it is for rogers.

RollTribe said:
OP... You can also run this http://dl3.htc.com/application/RUU_..._10.130.32.34_release_signed_With_Partial.exe ruu, this is the AT&T one. Options are good .
Click to expand...
Click to collapse
exad said:
Yes you should follow my directions above. Sorry for confusing you
After the RUU you have to do the OTA portion too or you won't update to 3.18 or 3.17 or whatever it is for rogers.
Click to expand...
Click to collapse
thank you for all your help guys. Im going to try it and report back. thanks!

RollTribe said:
OP... You can also run this http://dl3.htc.com/application/RUU_..._10.130.32.34_release_signed_With_Partial.exe ruu, this is the AT&T one. Options are good .
Click to expand...
Click to collapse
It is not recommended to run an RUU for a different carrier even if the hardware is almost exactly the same.
The device drivers may be slightly modified and I don't think canadian carrier and american carrier one x use the same radio bands. Whenever I use an AT&T radio, my phone gets crazy hot fast while using radio

Im getting error[170]: USB Connection error
I have USB debugging enabled.
Device manager sees the device.
i can adb

exad said:
It is not recommended to run an RUU for a different carrier even if the hardware is almost exactly the same.
The device drivers may be slightly modified and I don't think canadian carrier and american carrier one x use the same radio bands. Whenever I use an AT&T radio, my phone gets crazy hot fast while using radio
Click to expand...
Click to collapse
Oh I didn't know, my bad. I've always read that it's fine, but I guess it's better to be safe. H8 said it was fine, but OP can choose from what he thinks. I, personally, never had any problems but YMMV I guess.

buhbuh said:
Im getting error[170]: USB Connection error
I have USB debugging enabled.
Device manager sees the device.
i can adb
Click to expand...
Click to collapse
Try running the RUU while in fastboot.

buhbuh said:
Im getting error[170]: USB Connection error
I have USB debugging enabled.
Device manager sees the device.
i can adb
Click to expand...
Click to collapse
Also, try running it via a USB 2.0 port, not 3.0. I have all kinds of problems with 3.0.
Edit: nvm you got it working.

exad said:
Try running the RUU while in fastboot.
Click to expand...
Click to collapse
That worked.
It showing that my current image version is 1.94.631.3
Should I continue?
again sorry for asking soo many questions.

RollTribe said:
Oh I didn't know, my bad. I've always read that it's fine, but I guess it's better to be safe. H8 said it was fine, but OP can choose from what he thinks. I, personally, never had any problems but YMMV I guess.
Click to expand...
Click to collapse
You're probably right, it would probably be fine. I'm paranoid myself, and usually will go overboard with the old better safe than sorry frame of mind
---------- Post added at 09:09 PM ---------- Previous post was at 09:08 PM ----------
buhbuh said:
That worked.
It showing that my current image version is 1.94.631.3
Should I continue?
again sorry for asking soo many questions.
Click to expand...
Click to collapse
Yes, go through and let it do it's thing.

buhbuh said:
That worked.
It showing that my current image version is 1.94.631.3
Should I continue?
again sorry for asking soo many questions.
Click to expand...
Click to collapse
That should be fine, it's just your firmware version.
Edit: ah ya beat me to it.

RollTribe said:
That should be fine, it's just your firmware version.
Edit: ah ya beat me to it.
Click to expand...
Click to collapse
IM AN XDA POST NINJA BRO!!!
{
"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"
}

exad said:
IM AN XDA POST NINJA BRO!!!
Click to expand...
Click to collapse

[SOLVED] Can't update further (3.4 kernel)

Hello everyone,
I had installed CM10.1 some time ago, everything was good except some Wi-Fi problems which I somehow fixed with Bubba kernel. I decided to update my build after staying for a long time on the same one. So I downloaded the latest CM10.1 nightly, went on to install it, only to get surprised by a red sign on the recovery screen saying that the kernels don't match or is not compatible (or something similar). So I searched around to find a way to update my kernel but I was very confused with the guides I found, and as a result, I turned to TrickDroid with Sense 5, which I'm currently on.
It's time now to update again but I'm still confused about the whole thing. I have no idea where to start and that's the reason you're reading this thread right now.
My hboot is 1.13 and my baseband 0.16 (Europe). Also, I'm S-On and not SuperCID-ed.

Chris95X8 said:
Hello everyone,
I had installed CM10.1 some time ago, everything was good except some Wi-Fi problems which I somehow fixed with Bubba kernel. I decided to update my build after staying for a long time on the same one. So I downloaded the latest CM10.1 nightly, went on to install it, only to get surprised by a red sign on the recovery screen saying that the kernels don't match or is not compatible (or something similar). So I searched around to find a way to update my kernel but I was very confused with the guides I found, and as a result, I turned to TrickDroid with Sense 5, which I'm currently on.
It's time now to update again but I'm still confused about the whole thing. I have no idea where to start and that's the reason you're reading this thread right now.
My hboot is 1.13 and my baseband 0.16 (Europe). Also, I'm S-On and not SuperCID-ed.
Click to expand...
Click to collapse
Why not flash the boot.img from the New Build.zip as you are S-ON?

khan.orak said:
Why not flash the boot.img from the New Build.zip as you are S-ON?
Click to expand...
Click to collapse
Obviously I tried that with no luck.
But here's the thing. The CM thread says "you need to update your firmware to use the 3.4x kernel click me". I followed the tutorial provided and the update did not work. That's where I'm stuck.

Chris95X8 said:
Obviously I tried that with no luck.
But here's the thing. The CM thread says "you need to update your firmware to use the 3.4x kernel click me". I followed the tutorial provided and the update did not work. That's where I'm stuck.
Click to expand...
Click to collapse
Aahhh yess
Can you just run an RUU from your carrier? That's a one-stop solution: will upgrade your firmware and HBOOT and you should be good to go.
Sent from my HTC One S using Tapatalk 4 Beta

Can you guide me please?
I found a page with a bunch of RUUs but I don't know which one to run. Also, my One S was carrier locked but I unlocked it by following a tutorial I found in the forum. Does that mean I should run a carrier RUU?
Sent from my HTC One S using Tapatalk 4

Chris95X8 said:
Can you guide me please?
I found a page with a bunch of RUUs but I don't know which one to run. Also, my One S was carrier locked but I unlocked it by following a tutorial I found in the forum. Does that mean I should run a carrier RUU?
Sent from my HTC One S using Tapatalk 4
Click to expand...
Click to collapse
Okay. Sure.
First, You will have to tell me your CID. You can find that out by getting CID GETTER from play store. It should tell you your CID in RED color.
Also, you run the RUU, it will upgrade you plus get you on stock, afterwards, IF it is locked again, you can unlock it and flash CM latest nightlies again. So no biggie there.

Hey thank you very much for your time.
The app says my CID is H3G_001
Sent from my HTC One S using Tapatalk 4

Chris95X8 said:
Hey thank you very much for your time.
The app says my CID is H3G_001
Sent from my HTC One S using Tapatalk 4
Click to expand...
Click to collapse
I suppose that is Three (3) UK .
Okay, I found that there is no JellyBean RUU for your carrier. Same as they did with HTC One X.
But here's the deal, after relocking your bootloader, you can use This RUU which is an ICS RUU.
It will bring you to Stock ICS without changing your HBOOT and firmware. Afterwards, you should check for System Updates and receive JellyBean OTA. So that will take you to JellyBean + 2.15.0000 HBOOT + Newer Firmware.

OK so if I get it right... I lock my bootloader, run that RUU which will bring me back to ICS, update through OTA (does that work everywhere?) and then just do the rooting and recovery stuff again and install the latest CM build. Alright, I'll give it a shot!
Sent from my HTC One S using Tapatalk 4

Chris95X8 said:
OK so if I get it right... I lock my bootloader, run that RUU which will bring me back to ICS, update through OTA (does that work everywhere?) and then just do the rooting and recovery stuff again and install the latest CM build. Alright, I'll give it a shot!
Sent from my HTC One S using Tapatalk 4
Click to expand...
Click to collapse
Yeah, that's right.
Yes, udpdate through WiFi as it is a big update to JB OTA. works everywhere.
---------- Post added at 05:12 PM ---------- Previous post was at 05:10 PM ----------
Chris95X8 said:
OK so if I get it right... I lock my bootloader, run that RUU which will bring me back to ICS, update through OTA (does that work everywhere?) and then just do the rooting and recovery stuff again and install the latest CM build. Alright, I'll give it a shot!
Sent from my HTC One S using Tapatalk 4
Click to expand...
Click to collapse
Also, I'll advise that you do a complete backup after you update to JellyBean, as I can see no JellyBean RUU/OTA for your carrier. So in case of any problems, you can restore NANDroid backups.
So, after JB update, flash a custom recovery (TWRP 2.3.3.0 preferable), before rooting and any other stuff, do a complete backup of BOOT+SYSTEM.

khan.orak said:
Also, I'll advise that you do a complete backup after you update to JellyBean, as I can see no JellyBean RUU/OTA for your carrier. So in case of any problems, you can restore NANDroid backups.
So, after JB update, flash a custom recovery (TWRP 2.3.3.0 preferable), before rooting and any other stuff, do a complete backup of BOOT+SYSTEM.
Click to expand...
Click to collapse
You see, I got this One S from the UK locked to Three but I live elsewhere, so I unlocked with a method I found on the forums. Does the process change at all?

Chris95X8 said:
You see, I got this One S from the UK locked to Three but I live elsewhere, so I unlocked with a method I found on the forums. Does the process change at all?
Click to expand...
Click to collapse
nope. I think you should be able to unlock it using This method IF it locks after the update.
But before doing any stuff (unlocking, rooting etc), make nandroid backups of the new JB ROM. People have to strive really hard in absence of RUU, OTA.zip and NANDroids.

khan.orak said:
nope. I think you should be able to unlock it using This method IF it locks after the update.
But before doing any stuff, make nandroid backups. People have to strive really hard in absence of RUU, OTA.zip and NANDroids.
Click to expand...
Click to collapse
That's how I did it :laugh:

Chris95X8 said:
That's how I did it :laugh:
Click to expand...
Click to collapse
Great. shouldn't be a problem then.

khan.orak said:
So, after JB update, flash a custom recovery (TWRP 2.3.3.0 preferable), before rooting and any other stuff, do a complete backup of BOOT+SYSTEM.
Click to expand...
Click to collapse
From what I see, TWRP needs root to install now (with the GooManager app). When I first installed it, I did it with a fastboot command since the recover was an image file.

Chris95X8 said:
From what I see, TWRP needs root to install now (with the GooManager app). When I first installed it, I did it with a fastboot command since the recover was an image file.
Click to expand...
Click to collapse
what recovery do you have right now?

khan.orak said:
what recovery do you have right now?
Click to expand...
Click to collapse
TWRP actually. But it's ok, I found this. I thought the RUU would restore the HTC recovery.
Why do you suggest 2.3.0.0 though? Can't I update to the latest one (2.6)?

Chris95X8 said:
TWRP actually. But it's ok, I found this. I thought the RUU would restore the HTC recovery.
Click to expand...
Click to collapse
If you want to root your device, just flash a flashable SuperSU.zip from recovery. Instant root.
---------- Post added at 03:44 PM ---------- Previous post was at 03:39 PM ----------
Chris95X8 said:
TWRP actually. But it's ok, I found this. I thought the RUU would restore the HTC recovery.
Why do you suggest 2.3.0.0 though? Can't I update to the latest one (2.6)?
Click to expand...
Click to collapse
actually, I have been having issues with 2.6.0.0 flashing Carbon ROM. PACman worked fine. Can't say anything. Both worked okay with 2.3.3.0. You may give the latest a try.

Ughhh what the hell is this now. The RUU can't run.
I locked the bootloader, went on to run the RUU and this happened...
{
"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"
}

Chris95X8 said:
Ughhh what the hell is this now. The RUU can't run.
I locked the bootloader, went on to run the RUU and this happened...
Click to expand...
Click to collapse
Oh. Just yesterday, some folks reported unsuccessful and corrupt RUU downloads from androidruu site.
You may use this one Here

Chinese Fastboot Mode?

Hey everyone!
So, I flashed dalvik and bionic optimizations for the OnePlus One that I found over on the Nexus 5. When I booted back up into Android, all of my apps were missing, and everything kept on crashing. So, I booted into Fastboot Mode, but instead of the Cid logo which is usually presented, this message came up:
己进人fastboot...
{
"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"
}
The English translation is roughly "You have entered fastboot...". Everything still worked fine. I flashed my system partition back, and everything was okay. But, strangely, the Chinese fastboot message still appears instead of Cid. I kinda want Cid back...does anyone have any solutions? And yes, my phone is the international model.

i also have the same screen for fastboot. to make it worst i dont have root access but have a chinese version of cwm on the device. donno what to do.

darkmessiah said:
i also have the same screen for fastboot. to make it worst i dont have root access but have a chinese version of cwm on the device. donno what to do.
Click to expand...
Click to collapse
Is your fastboot still fully functional? When did this start showing up?

treChoy said:
Is your fastboot still fully functional? When did this start showing up?
Click to expand...
Click to collapse
Maybe you should flash bootloader from CM11S factory image. File name is sbl1.mbn
i have an chinese version OPO , my bootloader is cid after i flash stock image.
btw,it's 已进入fastboot. they are very similar.
sorry for my english
Sent from my One using XDA Premium 4 mobile app

Leicxan said:
Maybe you should flash bootloader from CM11S factory image. File name is sbl1.mbn
i have an chinese version OPO , my bootloader is cid after i flash stock image.
btw,it's 已进入fastboot. they are very similar.
sorry for my english
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Whoops, my bad, I was using handwriting input and didn't see that mistake good catch!
Playing around with bootloader is reaalllly dangerous stuff....I don't know if I want to go that far.

treChoy said:
Whoops, my bad, I was using handwriting input and didn't see that mistake good catch!
Playing around with bootloader is reaalllly dangerous stuff....I don't know if I want to go that far.
Click to expand...
Click to collapse
Well you can also try flashing the logo.bin partition from the CM11S image cyngn has at https://cyngn.com/products/oneplusone/, but if your bootloader is already in chinese, you might just want to flash the device back to full stock using the fastboot image.

ddggttff3 said:
Well you can also try flashing the logo.bin partition from the CM11S image cyngn has at https://cyngn.com/products/oneplusone/, but if your bootloader is already in chinese, you might just want to flash the device back to full stock using the fastboot image.
Click to expand...
Click to collapse
If I flash the fastboot image, will everything on my device be erased?

If you want i have 22r on zip

gro95qg said:
If you want i have 22r on zip
Click to expand...
Click to collapse
Again, will that erase everything on my OPO?

treChoy said:
Again, will that erase everything on my OPO?
Click to expand...
Click to collapse
Yes but i thinks your phone is a clon . Where do you buy it?
ps Sorry my enghish im french

gro95qg said:
Yes but i thinks your phone is a clon . Where do you buy it?
ps Sorry my enghish im french
Click to expand...
Click to collapse
I got it direct from OnePlus. I was a winner in the Storm of Invites.

oh great if you have a invit ...

gro95qg said:
oh great if you have a invit ...
Click to expand...
Click to collapse
There is a thread in the "GENERAL" section regarding invites. We have an invite list open, which will hopefully be opened back up in August.

treChoy said:
If I flash the fastboot image, will everything on my device be erased?
Click to expand...
Click to collapse
Yeah, it will fully revert your device to the factory image. Once you are done, if you have the 64gb model, make sure to flash the userdata_64gb.img manually after otherwise your system will only show as 16gb.

ddggttff3 said:
Yeah, it will fully revert your device to the factory image. Once you are done, if you have the 64gb model, make sure to flash the userdata_64gb.img manually after otherwise your system will only show as 16gb.
Click to expand...
Click to collapse
Yeah...that's a bit too much to lose just to change how my fastboot looks. Thanks for your suggestion though.

So upon further research, it looks like this is the exact same fastboot screen that OPPO devices use!! Somehow, I've gotten the OPPO fastboot mode one my One! And OnePlus denies involvement with OPPO....

How to root 11.0-XNPH30O?

Problem: I cannot root on 30O.
I have revived my OnePlus One from a soft-brick because I was trying to update from 25R to 30O from the rooted phone. Please refer to forum.xda-developers.com/oneplus-one/help/how-to-update-to-11-0-xnph30o-t2847037for more info. I have learned so much from it.
So after the soft brick, I restored it to 22R. Then an update came in for 25R, I followed the instructions to root the phone, root checker confirmed that I was indeed rooted. (I thought I still had TWRP) so I updated to 30O. I read that the 30O has another update after it, but I still have not received that update yet. When updated to 30O, I realized I can't use titanium back up anymore, and I no longer have SuperUser.
So I followed this video to do the root once again. https://www.youtube.com/watch?v=5O2e_R_TbVg&list=UUk1SpWNzOs4MYmr0uICEntg. But to no avail it doesn't seem to root. When I reboot into recovery mode, TWRP is also gone instead it shows the stock CM11S recovery.
The main reason, I wanted to upgrade to 30O was to be up-to-date, I got my wish! It's kind of ironic. But I still want to be rooted once more. If anyone can help, thank you in advance.
I will check this thread again tomorrow, I thank you for all that XDA members especially vamshi88 has been so persistent in helping me. These have been stepping stones for me as an Android user.

Is your bootloader unlocked? It should if you had twrp installed. Why don't you install twrp with fastboot and then simply flash supersu zip?
Sent from my A0001 using Tapatalk

boober78 said:
Is your bootloader unlocked? It should if you had twrp installed. Why don't you install twrp with fastboot and then simply flash supersu zip?
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I tried to unlock the bootloader in Fastboot Mode, but it doesn't wipe my entire device instead it just brings it to the lockscreen.. As if nothing happened. I followed the youtube video too.

can you put your phone in fastboot and try this command. It will tell you your fastboot status
fastboot oem device-info
Click to expand...
Click to collapse

playya said:
can you put your phone in fastboot and try this command. It will tell you your fastboot status
Click to expand...
Click to collapse
Okay, thank you. I will try this at home.

Do I have to press Shift+Right click and open command prompt in the OPO Toolbox folder? Or can I just do it in the cmd? I want to learn as much as possible from these instructions. Thank you for your patience.

skyhonor said:
Do I have to press Shift+Right click and open command prompt in the OPO Toolbox folder? Or can I just do it in the cmd? I want to learn as much as possible from these instructions. Thank you for your patience.
Click to expand...
Click to collapse
hey make life easy for you simply download a tool called minimal adb. Its great but just open up a cmd window in where your fastboot exe is located. Also you can simply click on thanks if anyone has helped you...

playya said:
hey make life easy for you simply download a tool called minimal adb. Its great but just open up a cmd window in where your fastboot exe is located. Also you can simply click on thanks if anyone has helped you...
Click to expand...
Click to collapse
I thank you and I will click the thanks button as soon as my 8 thanks limit has been lifted.:good:
I will download the minimal adb as you suggested as soon as I get home.

playya said:
can you put your phone in fastboot and try this command. It will tell you your fastboot status
Click to expand...
Click to collapse
It returned 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"
}
[/URL][/IMG][/IMG]
The problem is I cannot unlock the bootloader anymore. When I tried other Youtube methods regarding rooting the OnePlus One, I get stuck on the bootloader option and instead of wiping my data. It just reboots my device to the lockscreen. Thank you for understanding.

skyhonor said:
It returned this..
[/URL][/IMG][/IMG]
The problem is I cannot unlock the bootloader anymore. When I tried other Youtube methods regarding rooting the OnePlus One, I get stuck on the bootloader option and instead of wiping my data. It just reboots my device to the lockscreen. Thank you for understanding.
Click to expand...
Click to collapse
Oh nevermind! I'm such a dummy >.<! It says bootloader unlock true.. I missed this little detail, I was never good at logic in math.. I thank you all that has helped me root my device to 30O.