Database Info

[Q] Stock ROM 2.3.3 for Nexus??

Hi,
I need to make an unROOT and I cannot find original stock ROM for my 9023i Nexus S. I went through a lot of threads but there is no original ROM. I need to send it to servis and use warranty - so I probably need 2.3.3. I tried look for in out of xda and downloaded something that has 4MB - it does not work.
Please, if you have it, send me a link. Thank you!

forum.xda-developers.com/showthread.php?t=1063664
for unrot use youtube and google..

once you flash stock rom for your device with link from post above this one it will unroot and give you stock recovery

sean1984 said:
once you flash stock rom for your device with link from post above this one it will unroot and give you stock recovery
Click to expand...
Click to collapse
I read this. But what happend was, that I flashed it and the lock was opened at start - and when I got into the system, there were a lot of canceled processes and I couldnt continue Now I probably need to root it again (I hope it will work) but I dont know what to flash
EDIT: Great. I cannot get into system so I cannot enable debugging, - so I cannot root it again and eve get into system AND there is no recovery Only thing I can do is to connect USB cable and open disk in PC
Is there any way to push from bootloader recovery through adb???

Why would you flash 2.3.3 ? leting your device "officially" update to 2.3.6 or even ICS (if you're I9020T) isn't a guilt lol ..... Anything official and a locked bootloader , unrooted would be fine for warranty purposes ...

mahanddeem said:
Why would you flash 2.3.3 ? leting your device "officially" update to 2.3.6 or even ICS (if you're I9020T) isn't a guilt lol ..... Anything official and a locked bootloader , unrooted would be fine for warranty purposes ...
Click to expand...
Click to collapse
Never mind. I managed to get there 2.3.4. When the device comes back I root it again so no need to update right now.... anyway, I cannot relock it it does not have to be locked?
EDIT: I'd rather had it locked, just in case.... but I cannot relock it. I tried to use sdk, write "adb reboot bootloader" and then " fastboot oem lock" but both case the command line responded something like that it is not internal command etc. (I dont have it in English)

devcager said:
Never mind. I managed to get there 2.3.4. When the device comes back I root it again so no need to update right now.... anyway, I cannot relock it it does not have to be locked?
EDIT: I'd rather had it locked, just in case.... but I cannot relock it. I tried to use sdk, write "adb reboot bootloader" and then " fastboot oem lock" but both case the command line responded something like that it is not internal command etc. (I dont have it in English)
Click to expand...
Click to collapse
While you're in fastboot mode and connected to your PC , run "fastboot oem lock" .... This should lock it unless you're having another issue ...

mahanddeem said:
While you're in fastboot mode and connected to your PC , run "fastboot oem lock" .... This should lock it unless you're having another issue ...
Click to expand...
Click to collapse
"run fastboot oem lock" means to put it in a command line? Because it does not work. Or it is a program??

devcager said:
"run fastboot oem lock" means to put it in a command line? Because it does not work. Or it is a program??
Click to expand...
Click to collapse
it means you go into your command prompt , guide your way to where you put your sdk tools with the fastboot command, and then run the command from there.
so basicly start > run > cmd , and from there find go to your directory where you placed your android sdk tools.

kwaidan said:
it means you go into your command prompt , guide your way to where you put your sdk tools with the fastboot command, and then run the command from there.
so basicly start > run > cmd , and from there find go to your directory where you placed your android sdk tools.
Click to expand...
Click to collapse
I do exactly this... It does not work. when in command prompt I put "cd android-sdk-windows" and get there. then I put "fastboot oem lock" and it tells what I wrote in previous posts :/

[Q] EMERGANCY please help s4 based htc one x

i just got my one x today, unlocked bootloader, rooted, i followed the intructions at onexroot and was sucsessful, i dont know exactly what recovery it is, its file is called openrecovery-twrp-2.1.7-evita.img, anyways flashed sucsesfully and everything then i went to install a button mod, i cant find where i got it, anyways it said sucsessful, but when it booted it hangs at the one x screen, i was an idiot and failed to make a bake up, i clicked factory reset in recovery hoping to remove the bad file, no good, i downloaded a custom rom, but i cant put it on the sd because it wont mount, i get
* verifying filesystems...
* verifying partition sizes...
E:unable to mount /sdcard
E:unable to open ums lunfile: (no such file or directory)
please help im freaking out, what can i do to fix it

First turn off ur mobile ( hold down power button until it turns off)..then hold down power and volume down together... is it getting into the bootloader??
since u rooted and installed a custom recovery u must have used 'fastboot.exe' somewhere....did u ???

i have fast boot exe on my computer, im new to this but i dont think i can get it into adb shell, i tried, maybe did it wrong, sd wont mount and no backup like an idiot, and yes i can get into bootlaoder and recovery, thank you so much for quick response

after some fiddleing i can get it into fastboot and it makes the detected sound on the computer but adb still doesnt recogized it, it says no device found

There wil be no adb in fastboot....and i guess it is better to download a RUU(ROM upgrade utility)... its just a exe file...I guess downloading it and running it wil flash the stock ROM in ur phone and there wil be no problem i guess...

ive installed htc sync and am downloading the ruu, if its a earlier version does that matter? im not sure but i think it was at 1.85, or 1.75, the one i found is 1.73, and once downloaded what do i do, total noob, sorry, thanks again

I guess the RUU must be of same version.... Its better if u find the exact version..i am also a noob..so not sure about different version.. btw where did u search for RUU??
http://forum.xda-developers.com/wik...ashing_a_RUU_to_completely_restore_your_phone
http://forum.xda-developers.com/showthread.php?t=1543604

i typed the first command and its stuck at waiting for device???

Yo man dont freak out youre Phone is perfectly fine here take a detailed look at this link http://forum.xda-developers.com/wiki/HTC_One_X
And after that if you still can`t do anything go to youre specificc htc one x thread from the forum and post there those guys will help you faster and fail proof
I had a desire z and i remember that first you must boot the phone in download mode and then the ruu will find it anyway i wish you luck

it wont go into download mode

by first command which command do u denote?? and wat do u mean by download mode??

"fastboot getvar version-main"
somewhere in the myriad of xda threads ive read it said ruu required you to be in download mode, interstingly enough fast boot works on my mac partition, but not my windows, possibly an issue with windows 8 but idk

Possibly HBOOT driver issue oly....phone is in 'usb fastboot' oly right??? and does 'fastboot devices' list ur device??

it goes into fastboot usb, if i click bootloader it says hboot, but when i do adb it says device not found, i dont know where fastboot devices is listed

Phone should be displaying 'fastboot usb'.... Then oly fastboot.exe wil work.....and adb wont work both in 'fastboot usb' and 'hboot'....when in 'fastboot usb' ...in computer type the command 'fastboot devices'....does it list the devices??

it lists a serial number

note that all the drivers and files i have come from htc sync or onexroot.coms bootloader unlock and root pages

then fastboot mode is working fine...what recovery,kernel and ROM are u in...sometimes the problem u stated might occur due to kernel and ROM mismatch...For recovery i would recomend you to install ClockworkMod Recovery....

could you point me to one that works, ive tried 2 supposed cwm recovieries and they both hung at at the legal disclaimer, twrp is the only one that loads

may i know how r u installing the cwm recoveries??? and were u able to run "fastboot getvar version-main" ??

[Q] HTC one S Bricked and pissed !!

So in my infinite wisdom I decided to download one more ROM and successfully bricked my phone bootlooped and cant seem to anything with it !! I cant mount the SD card and I have tried everything I have seen on here from the Fast boot kit etc...any enlightenment from someone would be appreciated..I have CWM on my phone but can not get past the boot animation....nor can I download a new rom or boot img....:crying: btw I have been at this since 9 and it is now 4 30 AM !!!

You need to download the RUU file and run it from your pc
Sent from my HTC One S using xda app-developers app

Adb push a rom onto the phone and flash
Sent from a man, using a mobile phone

k1llacanon said:
Adb push a rom onto the phone and flash
Sent from a man, using a mobile phone[/
I tried this no success....
Click to expand...
Click to collapse

flash original recovery (can be taken from the RUU), Relock bootloader afterwards run RUU on your computer

septamobile said:
flash original recovery (can be taken from the RUU), Relock bootloader afterwards run RUU on your computer
Click to expand...
Click to collapse
Ok can someone please explain to me whats ruu...I have no idea what that is or where I can get it from !!!

Ruu takes the phone completely back to stock but u need to find the right version for u so we need some information
What country are you in?
What is your radio version
Is your phone branded? E. G does it have t mobile on it
Sent from a man, using a mobile phone

Okay download an appropriate ruu for your device, international, tmobile, etc. Power down the device (Power button and volume down for 10 seconds) plug in the usb from the wall and power on and charge for a few hours. (Don't want your phone to permanently turn off and hard brick your device) Follow the instructions on the ruu to get back to stock.
Relock your bootloader before starting the ruu process. "fastboot oem lock" You should know the basics by now.
I'll Pm you some ruu that may work..

i have messed everything
I accidentally formatted my internal storage , cache , data, system and everything.
I cannot able to mount the USB and not even fastboot as it is saying waiting for device. My bootloader is the only thing thats working,not even my philz recovery is of no use . adb is not recognizing my phone . please help me
Please let me know about any solution for the problem

kt92 said:
I accidentally formatted my internal storage , cache , data, system and everything.
I cannot able to mount the USB and not even fastboot as it is saying waiting for device. My bootloader is the only thing thats working,not even my philz recovery is of no use . adb is not recognizing my phone . please help me
Please let me know about any solution for the problem
Click to expand...
Click to collapse
First thing you need to do is get fastboot working. At this point, you cannot do anything without it.
So go into bootloader, select fastboot, connect to pc and you should see it change to fastboot USB on your phone after a few seconds.
Navigate to the folder containing fastboot and hold shift and right click somewhere on the window, select open command prompt here. Now, enter the command:
fastboot erase cache
If it goes through, great. If not, you need to update drivers. Install the latest version of HTC sync on your PC.
Of no luck, try another PC, different USB port, different cable, whatever. You need to get it working.
Once it is working, you will need to fastboot recovery, boot.img, etc, but do what I said first, then report back.
hTConeS | SoFF | DarKSeNsE | BuLLetprOOf
Dark Sense 5 Theme Updates+Tweaks
Inverted Sense 4+

Solved
ryanshew said:
First thing you need to do is get fastboot working. At this point, you cannot do anything without it.
So go into bootloader, select fastboot, connect to pc and you should see it change to fastboot USB on your phone after a few seconds.
Navigate to the folder containing fastboot and hold shift and right click somewhere on the window, select open command prompt here. Now, enter the command:
fastboot erase cache
If it goes through, great. If not, you need to update drivers. Install the latest version of HTC sync on your PC.
Of no luck, try another PC, different USB port, different cable, whatever. You need to get it working.
Once it is working, you will need to fastboot recovery, not.omg, etc, but do what I said first, them report back.
hTConeS | SoFF | DarKSeNsE | BuLLetprOOf
Dark Sense 5 Theme Updates+Tweaks
Inverted Sense 4+
Click to expand...
Click to collapse
yeah I followed the steps for making my bootloader work again , then i flashed RUU for my device and this worked without any error. I had the HTC__001 CID . soo it helped me in the RUU process
thanks for the solution

[Q] Bricked...Sorta....

Hi there, long time reader, possibly posted before but I cant remember my account name so I suppose I am a newbie.
1) Unlocked boot loader fine
2) Installed TWRP fine
3) Rooted fine
4) Installed CM11 and Gaaps
5) Restored all my apps from Titanium
Yaaaay ready to rock or so I thought. Only to be faced with "mobile network not available" so my intention was to flash another CM11 or other CM if it was possible to get it actually working to make phone calls. In my attempts to do this I cleared everything, so no OS. I can get into the bootloader and recovery mode still but that
ADB thing refuses to work. So as of now my PC cannot see the device to copy the rom files onto it.
Am I right in thinking if I get a USB OTG and put a rom on it, I can flash it from there??
I would settle for any custom rom at this stage that functions and doesnt have bloatware.
Failing that, would it be allowed here to ask for an image of a working htc one mini m4 to be uploaded somewhere that I can work with?
I wont be able to do anything until i get the USB OTG. Ive tried everything with ADB.
Your help would be so much appreciated.

hi,..
So first I´m not quite sure if an otg will work but it´s really worth to try it...
But after a (maybee) sucsessful flashing of a ROM via OTG there is no way around to get adb and fastboot to work.
Next I have to say is you should post some information about your phone.
h-boot Version
OS version
CID-Number if you know.
Only with this information sombody here can help you to find the right ROM.zip for flash trough recovery.
(if the firmware and the ROM do not match you are running in to multiple issues)
greets

Thank you
*** tampered ***
*** unlocked ***
M4_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.24.40e.00.26
OpenDSP-V19.2.0268.0927
OS--
eMMC-BOOT 1024MB

So,.....
It would be very interessting what firmware was on your device..
But as we can see the bootloader shows "OS- " so I suppose with h-boot 2.21.0000 it was 3.10.xxx.x.
I ran in same Problem a few weeks ago.
Recovery write: Can´t mount sd card and can´t mount data
I formated data in TWRP-recovery....(formated not only wipe...deletes everything on device).
As far as I remember after that adb returns to work and I sideloaded a new system.
I recommend you to flash first a stock or stock "near" system then and try to get s-off (to get rid of your problems)
But your first goal is to get a working OS on your device and get adb to work
A little help could be:
In fastboot mode :
"fastboot erase cache"
then reflash TWRP 2.7.1.1 with "fastboot flash recovery recoveryname.img"
If this don´t work out the only way is USB-OTG cable.
greets
edit: honestly I think the CM11 thing is a story after getting device back to life...
an other question ....what do you get if you type in adb when device is in recovery mode: "adb devices"
If needed here you can find a working sense 5.5 rooted stock rom (should work with your frimware) to start with:
http://androidfiles.org/getdownload...Jmz_M4_StockRooted_KK_Odex_WWE_3.10.631.5.zip
could help also:
http://forum.xda-developers.com/htc-one-mini/general/adb-fastboot-device-try-t2800519

shivasrage said:
So,.....
It would be very interessting what firmware was on your device..
But as we can see the bootloader shows "OS- " so I suppose with h-boot 2.21.0000 it was 3.10.xxx.x.
I ran in same Problem a few weeks ago.
Recovery write: Can´t mount sd card and can´t mount data
I formated data in TWRP-recovery....(formated not only wipe...deletes everything on device).
As far as I remember after that adb returns to work and I sideloaded a new system.
I recommend you to flash first a stock or stock "near" system then and try to get s-off (to get rid of your problems)
But your first goal is to get a working OS on your device and get adb to work
A little help could be:
In fastboot mode :
"fastboot erase cache"
then reflash TWRP 2.7.1.1 with "fastboot flash recovery recoveryname.img"
If this don´t work out the only way is USB-OTG cable.
greets
edit: honestly I think the CM11 thing is a story after getting device back to life...
an other question ....what do you get if you type in adb when device is in recovery mode: "adb devices"
If needed here you can find a working sense 5.5 rooted stock rom (should work with your frimware) to start with:
http://androidfiles.org/getdownload...Jmz_M4_StockRooted_KK_Odex_WWE_3.10.631.5.zip
could help also:
http://forum.xda-developers.com/htc-one-mini/general/adb-fastboot-device-try-t2800519
Click to expand...
Click to collapse
Thanks. adb devices will sometimes show the serial number I think, adb push CMupdate.zip I get "cannot read cmupdate.zip"
Fastboot flash recoery recovery.img works.
I have ordered a USB OTG so hopefully by friday I will have it. Im not sure how to show you the firmware? I thought I listed everything needed?

No, its not your fault...
Normaly firmware ist listed in bootloader under OS-3.10.401.3 (for example).
But sometimes after a bad flash when the partitions are messed up or so OS dissapears from bootloader like we can see in your case.
I know from HTC ONE M_7 that there are also some releases of TWRP-recovery that make dissapear OS-Numer from bootloader
but I don´t know if this is similar to the HTC One Mini.
If you get a a serial nuber from adb in recovery mode.. adb should work.....
Do you know how to sideload a ROM via adb and have you allready tried it?
greets

shivasrage said:
So,.....
It would be very interessting what firmware was on your device..
But as we can see the bootloader shows "OS- " so I suppose with h-boot 2.21.0000 it was 3.10.xxx.x.
I ran in same Problem a few weeks ago.
Recovery write: Can´t mount sd card and can´t mount data
I formated data in TWRP-recovery....(formated not only wipe...deletes everything on device).
As far as I remember after that adb returns to work and I sideloaded a new system.
I recommend you to flash first a stock or stock "near" system then and try to get s-off (to get rid of your problems)
But your first goal is to get a working OS on your device and get adb to work
A little help could be:
In fastboot mode :
"fastboot erase cache"
then reflash TWRP 2.7.1.1 with "fastboot flash recovery recoveryname.img"
If this don´t work out the only way is USB-OTG cable.
greets
edit: honestly I think the CM11 thing is a story after getting device back to life...
an other question ....what do you get if you type in adb when device is in recovery mode: "adb devices"
If needed here you can find a working sense 5.5 rooted stock rom (should work with your frimware) to start with:
http://androidfiles.org/getdownload...Jmz_M4_StockRooted_KK_Odex_WWE_3.10.631.5.zip
could help also:
http://forum.xda-developers.com/htc-one-mini/general/adb-fastboot-device-try-t2800519
Click to expand...
Click to collapse
shivasrage said:
No, its not your fault...
Normaly firmware ist listed in bootloader under OS-3.10.401.3 (for example).
But sometimes after a bad flash when the partitions are messed up or so OS dissapears from bootloader like we can see in your case.
I know from HTC ONE M_7 that there are also some releases of TWRP-recovery that make dissapear OS-Numer from bootloader
but I don´t know if this is similar to the HTC One Mini.
If you get a a serial nuber from adb in recovery mode.. adb should work.....
Do you know how to sideload a ROM via adb and have you allready tried it?
greets
Click to expand...
Click to collapse
Yes side load does not work.

I have a serious headache now. I tried so many roms and none of them let me make or recieve calls. The 3g mobile data is working. Would this work if the IMEI was blocked?
I also tried to update the firmware and ran into problems error 155 and error 132. I am really close to giving up.

[Q] Unlocked, reflashed, app ran into problem phone restarted and bricked?

Hi there,
Im still kinda a noob with android...
but i managed to unlock my htc sensation trough the steps @HTC,
changed the recovery, tried to flash a rom.
it failed due to my phone not being S-off. so i flashed it back :/
no problem there i thought just a rooted htc.
downloaded an app to remove bloat. and all seemed fine...
I was playing Clash of Clans, and it gave a message that the Google play services stopped and the phone rebooted.
when booted the lock screen was frozen, i pulled out the battery to find out my phone is unresponsive..
When i connect to windows 8, it cant recognize my phone at all
When i connect it to a charger i dont see the charging light.
and the worse thing is.. i cant get into the recovery.
any idea's what i can try?
i checked out the [unbrick] tread but i cant seem to figure out which "Package" i need and the links on the bottom of the page dont work when i click them
Thanks in advance
-Aline

At first you have not to be S-OFF in order to flash a rom.
Your rom will get installed just fine.You just need to flash the kernel of your rom manually through fastboot using the command fastboot flash boot boot.img.
What exactly do you mean by telling "so i flashed it back"?
Did you relocked your bootloader with fastboot oem lock and you flashed an RUU?
You said you are just rooted.If my theory was right you probably unlocked your bootloader again by flashing the unlock.bin and a cwm recovery and then you had to use a (Superuser , SuperSU zip).
The first time you unlocked your device was you using the same computer with windows 8?
If yes this is a problem.Check your device manager for unrecognised devices.Can you see the device?
Check this out.You can also check this.
(You can try with win7 or a linux destribution instead.)
Are you still able to boot into bootloader (hboot) using (Power)+(Vol-) Buttons?
If you have enabled usb-debugging and a working adb shell despite you are in a bootloop you can try:
Code:
adb shell
su ------>(If you don't see # instead of $)
reboot oem-78 -------> To get in RUU mode
or
reboot bootloader -------->(To reboot into hboot)
* reboot recovery could bring you to recovery *
If you can get into hboot or RUU mode give the command fastboot getvar all and copy-paste what it prints.

I know it was possible to flash with S-on,
thats what i tried and it failed (manually flashed the boot.img resulted in a bootloop)
so i flashed back to the "stock" rom.
resulting in a "normal" rooted device
since i've replaced my recovery and got root access
it never has been oem locked again.(still isnt)
i cant get into my bootloader/ruu mode. nor start up.
when i plug it into my computer (windows 8) it makes the sound as it does when you connect a device.
but in device manager it shows nothing, not even a yellow ! as it normally would if it can recognize a device.

aline1996 said:
I know it was possible to flash with S-on,
thats what i tried and it failed (manually flashed the boot.img resulted in a bootloop)
so i flashed back to the "stock" rom.
resulting in a "normal" rooted device
since i've replaced my recovery and got root access
it never has been oem locked again.(still isnt)
i cant get into my bootloader/ruu mode. nor start up.
when i plug it into my computer (windows 8) it makes the sound as it does when you connect a device.
but in device manager it shows nothing, not even a yellow ! as it normally would if it can recognize a device.
Click to expand...
Click to collapse
As you have not access to bootloader but your device is still seems to get connected i think you can only try HTC Unbricking Project.If the brickdetect.sh is not working you can try a different linux destribution.

Gatosbil said:
As you have not access to bootloader but your device is still seems to get connected i think you can only try HTC Unbricking Project.If the brickdetect.sh is not working you can try a different linux destribution.
Click to expand...
Click to collapse
Well, i just wonder which package i need, tried the links at the bottom of the post but those are no longer valid :/

aline1996 said:
Well, i just wonder which package i need, tried the links at the bottom of the post but those are no longer valid :/
Click to expand...
Click to collapse
Oups!I downloaded those packages some days before and I didn't see the links are broken now.
You can download them from the attachments here.
For Sensation and Sensation 4G

Gatosbil said:
Oups!I downloaded those packages some days before and I didn't see the links are broken now.
You can download them from the attachments here.
For Sensation and Sensation 4G
Click to expand...
Click to collapse
Well im afraid my phone is offically dead
this is what i get when i use ./brickdetect
[email protected]:/media/sdc$ ./brickdetect.sh
Searching for bricked device...
Device can't be detected. Check connections
[email protected]:/media/sdc$
please tell me i did something wrong xD
edit:
after some digging in knoppix i did find this:
http://imgur.com/DR7T4QK