There are several thread, especially one that contains an instruction on howto downgrade the HBOOT version.
Many users are not aware of the difference between an AMOLED and a SLCD Nexus device. The EPF30 ROM, is a special ROM, containing an image that WILL BRICK Nexus One devices that are of the SLCD generation!
The MICROP will be downgraded from 0c15 to 0b15, resulting in an irrecoverable flash, that will let the trackball light up in red, the only solution is to send it back to factory and let them fix it.
A lot of problems people are running into, is when they follow a downgrade instruction made by Nexus One owners, that have an AMOLED device and upgraded to boot version 0.35 by accident.
Wiki updated with a visible warning in the guide and reference to this thread.
Jack_R1 said:
Wiki updated with a visible warning in the guide and reference to this thread.
Click to expand...
Click to collapse
Very cool
Correct me if I'm wrong, but I think the first stock ROM to support SLCD was FRF91. I don't know if *all* versions of FRF91 support it or only the versions that came with said devices. But do *not* ever try to install an older version than FRF91 on your SLCD phone.
Stock FRF91 didn't support SLCD, only Korean and Vodafone versions of it. First Google ROM to support SLCD was unofficial FRG33 and official FRG83.
Jack_R1 said:
Stock FRF91 didn't support SLCD, only Korean and Vodafone versions of it. First Google ROM to support SLCD was unofficial FRG33 and official FRG83.
Click to expand...
Click to collapse
Great thanks. I think also the Mobilicity and Videotron Nexus Ones ship with a version of FRF91 and SLCD.
So if you mis-flash an SLCD phone there's no way out? You couldn't even try and blind-flash PASSIMG.ZIP?
Not if you just mis-flash, but if you downgrade HBOOT, which is not to be confused with flashing ROMs - and flash a very specific old OS build.
cmstlist said:
Great thanks. I think also the Mobilicity and Videotron Nexus Ones ship with a version of FRF91 and SLCD.
So if you mis-flash an SLCD phone there's no way out? You couldn't even try and blind-flash PASSIMG.ZIP?
Click to expand...
Click to collapse
If you look at eh EPF30, you'll find an image that is ment to flash microp code.
So - regardless on how many wipes and PASSIMG flashes you make, you'll never get to fix that, since till this very moment there's no SLCD ROM that contains a similar image to upgrade again.
This is why I opened this thread. the only way - is the hard way - to learn this. Because you'll hardly find that documented, or at least stated very clear. Thats why sticky threads with brick potential are dangerous imo
Okay thanks. For the benefit of the uninitiated, can you clarify exactly what is the function of the "microp" code and why this downgrade makes the N1 unrecoverable?
I saw one history by one guy on another forum.
He got some problems with nexus (something wrong with hboot), so he have flashed Eclair full stock rom on slcd nexus (I wonder what he was thinking about..). After flashing he got a brick with red-trackball.
But he says, that putting passimg.zip (korean one) solved it:
After power-on phone automaticly entered bootloader, founded passimg, checked it and started update procedure without any promt. Now the phone boots and works, but still have some problems with flashing custom roms (stuck on boot). Btw he says that red-trackball lighting didnt gone... so be carefull
cmstlist said:
Okay thanks. For the benefit of the uninitiated, can you clarify exactly what is the function of the "microp" code and why this downgrade makes the N1 unrecoverable?
Click to expand...
Click to collapse
Microp stands for microprocessor i suppose. Amoled have 0b15 version, SLCD do have 0c15. The only impact i know, is that the trackball will constantly light up in red, as there is a system warning.
Microp - microprocessor?
I think microp means microprogram.
For example, low-level driver, bridge between hboot and radio
It is possible to fix the red trackball: http://forum.xda-developers.com/showthread.php?t=847499
Tim4 said:
Microp - microprocessor?
I think microp means microprogram.
For example, low-level driver, bridge between hboot and radio
Click to expand...
Click to collapse
Better bad english than bad knowledge.. as I said, not sure, but your definition makes way more sense than my assumption.
Rusty! said:
It is possible to fix the red trackball: http://forum.xda-developers.com/showthread.php?t=847499
Click to expand...
Click to collapse
Not for everybody... The misc flash does not help in case you included the led image from epf30
Newbie question
Sorry for the newbie question I am a long time winmo user about to make my first jump into an actual android phone after playing with android for a while on my HTC HD so I bought a used Nexus one on ebay the other day and it should be here by the weekend. How do i make sure its AMOLED and not SLCD? Is there a boot-loader code or another way to know based on manufacturing dates etc. or are all N1's AMOLED as I understood them to be till now, though this thread seems to suggest otherwise. Thanks for the help and patience.
If you install an older recovery, that will let you know for sure. It won't harm the phone, but the screen won't work in recovery mode. Installing a newer recovery with fix again.
Amon started supporting SLCD at 1.8.0.1
Clockwork started supporting SLCD at 2.5.1.1
Sent from my Nexus One using XDA App
mo976 said:
Sorry for the newbie question I am a long time winmo user about to make my first jump into an actual android phone after playing with android for a while on my HTC HD so I bought a used Nexus one on ebay the other day and it should be here by the weekend. How do i make sure its AMOLED and not SLCD? Is there a boot-loader code or another way to know based on manufacturing dates etc. or are all N1's AMOLED as I understood them to be till now, though this thread seems to suggest otherwise. Thanks for the help and patience.
Click to expand...
Click to collapse
When you boot into the bootloader (i.e., hold the trackball down and power up the device), check the microp. If it its 0b15, it is AMOLED, if it is 0c15, is is SLCD...
Thanks Ill do that.
So how do I know which screen I have, I have the korean nexus one and since i got it I have never been able to get into the recovery screen. I do have it unlocked.
i234.photobucket.com/albums/ee97/xx_ed_xx/DSC02189.jpg
Related
It states in the relases notes that "Not vulnerable to the "one click root" exploit"!
Is he talking about Recovery Flasher that was just leaked/released.
Basically can i use Recovery Flasher and then Flash this Rom right after with No SPL Change or Radio Change From a Never Rooted Phone
What it means is that kernel was patched against this volunerability. You can flash recovery and then this rom but if you were to try using one-click afterwards it would not let you since cyan patched it. Shouldn't matter though cause if you're flashing this rom you already have root.
answer
He is talking about the kernel vulnerability that allows the one click rooting program to work.
If you don't have a rooted phone and have received no patches or security updates from your carrier, then you are able to take advantage of the vulnerability with the one click root program because if you will flash 4.0.1 after you exploit the kernel vulnerability.
I would suggest upgrading to the hard spl or engineering spl at the very least and the danger spl only if you plan to run a hero ROM. I would also suggest upgrading to the latest radio so you can take advantage of improved wireless capabilities (ie better reception, bluetooth etc)
Thanks Both of you im thinking of rooting but dont know if it would be worth it since last time i did i got a brick but i was so dumb and full of myslef after rooting i flashed the danger spl without upgrading the radio and just booted up my phone without going into recovery
Sorry Direct i found the semi relevant post to this one that you were helping out a bunch of noobs
No problem, hope you found what you were looking for somewhere at least.
You might want to take a look at nephron's latest guide. It is really n00b friendly, well written, and updated with all the latest tips and tricks that everyone has amassed since October and months of rooting/modding.
Check it out and good luck.
http://forum.xda-developers.com/showthread.php?t=548924
DirectMatrix said:
No problem, hope you found what you were looking for somewhere at least.
You might want to take a look at nephron's latest guide. It is really n00b friendly, well written, and updated with all the latest tips and tricks that everyone has amassed since October and months of rooting/modding.
Check it out and good luck.
http://forum.xda-developers.com/showthread.php?t=548924
Click to expand...
Click to collapse
Omg awesome thread cover just about everything including sd partitons which is what ive been searching for thanks alot
Original question(s) seem to be solved.
Closing thread
Hey everyone, I'm new to this forum. So...Hi
Anyways, I've got a problem with my Rogers Htc Dream. I was trying to root it and was following a guide on youtube. Then i realized rooting for T-Mobile G1s and Rogers HTC Dreams were different. Now i notice when i turn on my phone it shows a T-Mobile screen instead of the regular Rogers loading screen. I guess i installed the T-Mobile firmware on my phone. I checked in settings the current firmware im running is now 1.0. So, i'm wondering if anyone can help me put back on rogers firmware on my phone and also link me to a Rogers HTC dream rooting guide. Thanks in advance.
Slaii1030 said:
Hey everyone, I'm new to this forum. So...Hi
Anyways, I've got a problem with my Rogers Htc Dream. I was trying to root it and was following a guide on youtube. Then i realized rooting for T-Mobile G1s and Rogers HTC Dreams were different. Now i notice when i turn on my phone it shows a T-Mobile screen instead of the regular Rogers loading screen. I guess i installed the T-Mobile firmware on my phone. I checked in settings the current firmware im running is now 1.0. So, i'm wondering if anyone can help me put back on rogers firmware on my phone and also link me to a Rogers HTC dream rooting guide. Thanks in advance.
Click to expand...
Click to collapse
Yeah I have that too.
Not really an issue. I just too happy to care when I finally rooted my Dream.
Outblaze said:
Yeah I have that too.
Not really an issue. I just too happy to care when I finally rooted my Dream.
Click to expand...
Click to collapse
Okay so, the root worked for you? Everythings alright its just the start up screen that changed?
To get back to stock rogers firmware apply the update from rogers found here:
http://rogers.com/techsupport/
Then follow this guide to get your phone rooted and install cyanogenmod:
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Rogers_Dream_EBI1_to_CyanogenMod
beav_35 said:
To get back to stock rogers firmware apply the update from rogers found here:
http://rogers.com/techsupport/
Then follow this guide to get your phone rooted and install cyanogenmod:
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Rogers_Dream_EBI1_to_CyanogenMod
Click to expand...
Click to collapse
I'm abit scared to follow that guide because there seems to be some ifs about it, like it says avoid anything that writes to the kernel, otherwise you're dead. And it says you require a EBI1, how do I check if I have EBI1
"The Recovery Flasher utility will only work if you're on a version of Android that Rogers/HTC hasn't yet fixed.
If you are at the recovery screen, move on to the next step."
Well how do I know if they haven't fixed it? And if we can't use fastboot to flash images, as Rogers prevents it, then if this procedure goes south we're stuck? I can verify the MD5 of the SPL update ZIP 20 times, but that's not going to guarantee that when I flash it it's not going to brick my phone
edit: I booted with camera and power and it says hboot is 1.33.0009, does this mean I don't have to risk bricking when I root? The tutorial is for 1.33.0010.
I think that it makes it sound a bit worse than it is. I have never tried it but from what I have read if you boot a EBI0 kernel with a EBI1 radio it will just freeze. You will just have to pull out the battery, boot into recovery and then flash a EBI1 kernel on top.
Rogers is bad for releasing updates for their devices. All their Android devices still run cupcake, even the new LG Eve. This is to our advantage because none of the rogers firmwares are fixed. You can give the Recovery Flasher a try because the worst that will happen if you have a fixed rom is nothing.
If you have a 0009 spl you can follow the guide here to update your spl and recovery then start following the guide at Installing HTC System Image. You could also just use the method on the wiki for 0010, I cant see any reason that wouldn't work.
My phone is perfectly fine after the gaining root. So far not much of a difference, except for the virtual keyboard and two more screens and a few more apps and options.
beav_35 said:
I think that it makes it sound a bit worse than it is. I have never tried it but from what I have read if you boot a EBI0 kernel with a EBI1 radio it will just freeze. You will just have to pull out the battery, boot into recovery and then flash a EBI1 kernel on top.
Rogers is bad for releasing updates for their devices. All their Android devices still run cupcake, even the new LG Eve. This is to our advantage because none of the rogers firmwares are fixed. You can give the Recovery Flasher a try because the worst that will happen if you have a fixed rom is nothing.
If you have a 0009 spl you can follow the guide here to update your spl and recovery then start following the guide at Installing HTC System Image. You could also just use the method on the wiki for 0010, I cant see any reason that wouldn't work.
Click to expand...
Click to collapse
I really want to root so I can install applications to the memory card, and to get 1.6, but I'm really really really scared that it's going to break. I got the phone from ebay, so I'm pretty sure if it breaks I'm out $300 bucks. I'm really at a cross road here!
Ya i was kinda scared the first time too. Then I just bit the bullet and did it. Try to read through the forums as much as you can to learn as much as you can about how your phone works. Also make sure that you understand each step completely and what it is doing to your phone. This is what I did and it made me feel a lot better about the process.
The main risk is flashing the radio and spl once you are done that the chance of bricking is almost none of not none. If you have any questions that you can't find answers to by yourself just ask and me or someone else on the forum will answer them for you.
Yeah, if you're on the Rogers HTC dream, just follow the Rogers heres your real root thread, and all the guides he post. And follow it while filling in the rest with logic.
You'll probably get lost like I did, don't be afraid to ask around.
does anyone know the warranty if it bricks?
Hey everyone, thanks for the help. I went through with the root and everything seems to be working fine. I can make phone calls and everything. I'm running a hero rom. The only thing thats different is it shows a T-Mobile screen instead of Rogers. I don't think thats a big deal, is it?
QQ regarding this:
Are all SGS devices sufficiently similar enough such that a custom ROM for one (say the VzW Fascinate, or a Euro version) will be directly usable by others, or will what differences there are in hardware build (e.g., internal memory, camera flash vs. none, etc.) fragment efforts in the developer community enough that custom ROMs will be slower to achieve?
The Captivate intrigues me since an unlocked version should be very usable in Europe (and for getting rid of ATT bloatware as well as all the other fixes a rooted phone is likely to get before ATT bothers to do so).
They should all be the exact same internally, meaning the same rooting procedure of the european galaxy S, should also apply on the att version or any other version for that matter, and i hope so cause on the 18th im getting a captive woot =]
rafyvitto said:
They should all be the exact same internally, meaning the same rooting procedure of the european galaxy S, should also apply on the att version or any other version for that matter, and i hope so cause on the 18th im getting a captive woot =]
Click to expand...
Click to collapse
im getting a captivate too, however, there are some differences between the hardware and internal guts between the phones. To name a few, Storage Space, Flash for rear camera, and the front facing camera.
These could affect the internal guts/firmware on the device.
But lets hope we can get a sweet and fast root
Non of the gsm versions have flash beside the camera, ROM capacity and the front facing camera hardware have nothing to do with the rooting of any android device, im almost 100% that the european samsung galaxy S rooting procedure will work on any other samsung galaxy S variation.
We'll know soon enough...perhaps even within a week of the Captivate's release (hey, that's an interesting play on words).
The rooting procedure will work - however the recovery mode my be crippled as the M110S (Korea) version is. Need to wait for a custom recovery - or use ODIN to flash.
But if you dont have backup of the old firmware it might be more difficult to root.
Anyways the samsung version of android is in general pretty easy to root. (no locked bootloader etc)
For all intents and purposes the Vibrant/Captivate should be identical in every aspect except for accessories. (Wonders why those forums weren't just merged together). TMobile's 3G bands are different, too.
There's already a quickie root file posted by justadude over in the Vibrant forum. One file in the .zip needs to be updated to reflect the Captivate model number (SGH-I897) but in theory, it should work.
http://forum.xda-developers.com/showthread.php?t=723479
Here is the edited and signed root update. Anyone with a Captivate care to try? It's the Vibrant root with the AT&T model added, so it should work
For reference the Captivate is the SGH-I897
so rename this to update.zip place in the root of the SD connect to adb and type adb reboot recovery and select "Reinstall Packages" using the volume keys and power to select
EDIT: removed the update.zip please see this post for the updated one
nvm 10char
**double post**
xdaapp crash :-0
tried the signed update.zip and it didn't work for me.
@chaoscentral - I think your updater script is using DOS-style CRLF end of line characters. Try changing it to LF.
@zakdeutsch - Is that a Fascinate? I see ro.build.fingerprint = "verizon..."
Nope, certainly a captivate
I tried it on a Samsung Captivate and also had no luck.
wimbet said:
I tried it on a Samsung Captivate and also had no luck.
Click to expand...
Click to collapse
How do you have one already?
Regardless I hope this thing is rootable fairly quickly.
TexUs said:
Regardless I hope this thing is rootable fairly quickly.
Click to expand...
Click to collapse
Ditto. I'm thinking, though, that we're not going to see much movement on the root front till after release...
Anyone wanna give this one a try? I had edited the update script in wordpad before which I'm sure added some kind of funky formatting. So I made this one in ubuntu and signed it in windows(since I cant figure that one out in ubuntu)
This should work though, and keep in mind it only has the model numbers for the Captivate, no fascinate or epic 4g or vibrant
Hi to All,
Is it feasible now to install the Nexus One Android 2.2 on the Captivate?
Thanks
Muhamadabdelaall said:
Is it feasible now to install the Nexus One Android 2.2 on the Captivate?
Click to expand...
Click to collapse
No. I don't even know if anyone has even had a good look at the Captivate bootloader yet. Reportedly there is a FroYo ROM dropping very soon for the Korean Galaxy S and possibly soon for the US versions as well. Bodes well for getting 2.2 on the phone in the not-so-distant future. Probably.
My friend purchased an SLCD version of Nexus One from Korea. Without acknowledging that fact, I flashed a rooted Froyo through ROM manager (just the Stock Froyo option given). And then this tragedy has begun, they call it an SLCD Brick in the Desire forum.
So SLCD version owners, don't flash any ROMs posted here yet, not that they're bad - they're GREAT, just don't support SLCD screen yet.
And much HELP needed from devs to dig into this issue and resolve it (the desire forum already has plenty of resources, guess it won't be that hard...maybe)
update3: I've entered an issue in the CM tracker, id 2104
update2: now that my friend needs to use the phone, I have no other ways to get around the problem other than fastboot pushing the Korean stock Froyo image (system.img, boot.img, userdata.img). If anyone else needs it, I'll post it here, or just simply google it. Hope the devs can resolve this problem in the future
update: a good news is that Koush's actively working on a Clockwork Recovery image that supports the SLCD screen
Update: Solved by installing the korean (kt) frf91 just as you did. Now I'm waiting for some news regarding a slcd recovery + mod.
Does the SLCD have a more sensitive touchscreen?
I beleive the new Amon_ra 1.8.0.1 supports SLCD. Its just that, there are no roms right now that supports SLCD.
Similar thread here....
I think from what I can gather, they have found a 'fix'
http://forum.xda-developers.com/showthread.php?t=769794
kpjimmy said:
Similar thread here....
I think from what I can gather, they have found a 'fix'
http://forum.xda-developers.com/showthread.php?t=769794
Click to expand...
Click to collapse
Hope so, I'm still waiting for verification that it's true.
Quite happy with myself though. Just managed to get root on my stock FRF91 SLCD N1 without wiping and it still booting normally!
Just need a custom ROM now.
Hello everyone,
First of all, I am really sorry if this is a double post ( It probably is). I have honestly tried to search a response in already existing posts and I have found that some people seem to have experienced similar issues. However, being a total newbie in development, not really understanding the whole logical structure, I was unable to efficiently transfer existing responses to my problem. Thus, if somewhere exactly the same problem was already discussed I would be glad to read the thread. In opposite, similar threads will probably not help such an ignorant as I am.
That's said, here is the problem :
I have a HTC incredible S with the following status :
Alpharev
VIVO PVT SHIP S-OFF RL
HBOOT-1.09.1000
RADIO-38.02.01.11_M
eMMC - boot
february 11 2011.....
Android 2.2.1
As the pro's have already understood I have used the Alpharev method to switch my phone into "S-OFF" and root it around a year ago. As far as I remember I haven't done anything more. If I'm using the words right, no flash of recovery partition or anything of this kind. The phone is all right - no major issues.
Recently I have tried to update the phone, finally accepting the suggestion which was annoying me for several months. I have just accepted the update to Android 2.3 using OTA (I hope to use this right, I mean that the phone had downloaded the update itself, without pc or anything else).
Unfortunately the update failed ( blocked with a black background, the phone in the middle and a red triangle on the top right corner of the phone). After waiting for a very long time, I have removed the battery and put it back - everything is ok. (no update off course)
So the questions :
1. Is it theoretically possible to use official updates while being rooted? I don't really have time to play with different ROMs, an official ROM with root access is enough for me.
1.1 If yes, how?
2. If no, can I unroot it, update it and root it again in order to have the last official update with root?
2.1 If no, I suppose that I have to use "Custom ROMs". Could you please give me a link with the most up to date method to install Custom ROMS and may be an advice of a really STABLE one?
3. What options I haven't thought about?
Once again, I understand that all this was for sure already discussed, but I was probably unable to understand it.
Thanks a lot for all future responses!
SuperTraxer said:
Hello everyone,
First of all, I am really sorry if this is a double post ( It probably is). I have honestly tried to search a response in already existing posts and I have found that some people seem to have experienced similar issues. However, being a total newbie in development, not really understanding the whole logical structure, I was unable to efficiently transfer existing responses to my problem. Thus, if somewhere exactly the same problem was already discussed I would be glad to read the thread. In opposite, similar threads will probably not help such an ignorant as I am.
That's said, here is the problem :
I have a HTC incredible S with the following status :
Alpharev
VIVO PVT SHIP S-OFF RL
HBOOT-1.09.1000
RADIO-38.02.01.11_M
eMMC - boot
february 11 2011.....
Android 2.2.1
As the pro's have already understood I have used the Alpharev method to switch my phone into "S-OFF" and root it around a year ago. As far as I remember I haven't done anything more. If I'm using the words right, no flash of recovery partition or anything of this kind. The phone is all right - no major issues.
Recently I have tried to update the phone, finally accepting the suggestion which was annoying me for several months. I have just accepted the update to Android 2.3 using OTA (I hope to use this right, I mean that the phone had downloaded the update itself, without pc or anything else).
Unfortunately the update failed ( blocked with a black background, the phone in the middle and a red triangle on the top right corner of the phone). After waiting for a very long time, I have removed the battery and put it back - everything is ok. (no update off course)
So the questions :
1. Is it theoretically possible to use official updates while being rooted? I don't really have time to play with different ROMs, an official ROM with root access is enough for me.
1.1 If yes, how?
2. If no, can I unroot it, update it and root it again in order to have the last official update with root?
2.1 If no, I suppose that I have to use "Custom ROMs". Could you please give me a link with the most up to date method to install Custom ROMS and may be an advice of a really STABLE one?
3. What options I haven't thought about?
Once again, I understand that all this was for sure already discussed, but I was probably unable to understand it.
Thanks a lot for all future responses!
Click to expand...
Click to collapse
The AlphaRevX S-OFF HBOOT is preventing the OTA from getting applied successfully.
You are better off keeping S-OFF and using custom ROMs. You just need to install a custom recovery such as 4EXT Touch or ClockworkMod in order to flash custom Roms.
Thanks,
so:
1.NO
1.1 N/A
2 Probably yes, but inefficient/difficult
2.1 That's the way to go.
That's said, the phone is S-OFF, Rooted, and now I need to install custom recovery... hmmmm, where can i learn more about? Which one do you advice?
Thank you!
One more, not directly related.
Is it better to keep the current version of alpharev and hboot or is it better and possible to somehow update those parameters before installing the custom recovery?
SuperTraxer said:
One more, not directly related.
Is it better to keep the current version of alpharev and hboot or is it better and possible to somehow update those parameters before installing the custom recovery?
Click to expand...
Click to collapse
I personally like 4EXT Touch recovery. It should be available in the Android Market/PlayStore or you can check out the link in my signature.
As for the AlphaRevX HBOOT, I would just keep it installed.
tpbklake said:
I personally like 4EXT Touch recovery. It should be available in the Android Market/PlayStore or you can check out the link in my signature.
As for the AlphaRevX HBOOT, I would just keep it installed.
Click to expand...
Click to collapse
Thank you very much! Have just installed this! Will now try with ROMs! Thank you
SuperTraxer said:
Thank you very much! Have just installed this! Will now try with ROMs! Thank you
Click to expand...
Click to collapse
If you're looking for a good custom rom with the latest everything, try Venom ViperVIVO