I'm not having a very good day with my phone.
I had recently rooted my phone with a LiveCD rooter, and had decided I wanted Jelly Bean on my D2G. I tried to flash CyanogenMod (cm-7.2.0-droid2we.zip) to it, and now it won't start.
I took the liberty of running logcat while it starts. It appears to be caught in a loop about something called "flinger", here is a copy of the log output (I'm assuimg no "bad" information will be in bootup logs), it contains a few cycles of the loop: pastebin dot com/GtiqmJFm
This is what looks to be the actual error/panic:
E/FramebufferNativeWindow( 1864): couldn't open framebuffer HAL (No such device)
I/DEBUG ( 1560): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 1560): Build fingerprint: 'verizon/droid2we_vzw/cdma_droid2we/droid2we:2.2/S273/2.4.330:user/ota-rel-keys,release-keys'
I/DEBUG ( 1560): pid: 1864, tid: 1872 >>> system_server <<<
I/DEBUG ( 1560): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0000005c
I didn't change the bootloader (in fact when I go to flash the bootloader, I get error RX(7): [02]ERR[1e]G[03] when flashing VRZ_A955_2.3.20_1FF_01.sbf with sbf_flash, the screen says CRITICAL ERROR FEBE 0047.
I'm not looking to use the phone on a different carrier, I just want to overclock it to squeeze a few more months out of it, and possibly have Jelly Bean installed, and I'm pretty sure CyanogenMod has Jelly Bean.
Has anybody encountered this kind of issue before and can point me in the right direction?
CM7 is Gingerbread.
CM9 is Ice Cream Sandwich.
CM10 is Jelly Bean.
Official CM7 builds are made for 2.4.x firmware. They won't work with 4.5.x.
There are no CM10 builds for the D2G.
Gasai Yuno said:
CM7 is Gingerbread.
CM9 is Ice Cream Sandwich.
CM10 is Jelly Bean.
Official CM7 builds are made for 2.4.x firmware. They won't work with 4.5.x.
There are no CM10 builds for the D2G.
Click to expand...
Click to collapse
you know why when I use the 2.4.330 firmware, boot my phone in bootloader and not restart?
Because you cannot downgrade a device that was updated to 4.5.629.
Gasai Yuno said:
Because you cannot downgrade a device that was updated to 4.5.629.
Click to expand...
Click to collapse
so... is impossible instal cm7.2 in my device?
use unofficial cm7
http://rootzwiki.com/topic/4922-cm7-for-droid2-global-users-thread/#entry113470
Sent from my MB870 using xda premium
you have flash sbf file ginger 2.3.3 ....608 , afther flash botloader unbloked (desbloqueo de botloader ) .
PHP:
the bootloader can not be unlocked
Related
Hello guys,
Recently I bought HTC Desire S and the ROM on it is Cyanogenmod 7.2.
Now I am trying to install on official version of android 4.0.3. I downloaded the RUU from htcdev.com
RUU_SAGA_ICS_35_S_HTC_Europe_14.01.401.2_Radio_20.76.30.0835_3831.19.00.110_release_275068_signed
Click to expand...
Click to collapse
I plug the phone in PC and start the RUU, click few next buttons... till i get to the window to the Current information about your androud phone:
It says I got a ROM verson 2.10.401.4 and it needs to be updated to 14.01.401.2 (check picture 1)
After I click the next button and the wizard starts to update my phone. (check picture 2)
After one minute of that updating process I get the following error: (check picture 3)
ERROR [155]: Unknown Error
The only thing i can do is click recovery which doesn't help at all ....
Information about bootloader:
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.02.0002
RADIO-3831.19.00.110
eMMC-boot
Recovery is 4EXT Recovery 2.2.7 RC5
So my question is what am I doing wrong, and how can I install official version of android on my phone.
Tnx for answers,
You want STOCK rom or is it just Sense 3.6 that interests you ?
If it's just for Sense 3.6, there are few customs roms all around here. but you're S-ON so you'll need to flash boot.img independently via adb..
Instead if you want a completly stock rom you can check this thread.
Ok, I relocked the bootloader now I am in updating process. I will tell you what will happend
Till now everything looks okay
Great, if update began then you shouldn't have any prob
XDApped from my pimped Desire S
Hi,
I have some problem with my desire s, hope someone can help me. I couldn't start any of the 4.2.2 roms (stuck at boot screen), so I tought that I have a hitachi panel. Unfortunately I didn't checked then, now I know that my desire s have a sony panel. Anyway, I have uploaded the mddi kernel after flashing a rom and it didn't helped. Then I was fed up with seeing roms trying to boot up so I decided to get back to a 4.0 rom or something.
This went well, I can boot up all of them but I don't have wifi at all! Logcat says the following when I try to enable wifi:
E/WifiStateMachine( 1614): Failed to load driver!
E/WifiStateMachine( 1614): DriverFailedState
Is there anything I can do? What kernel should I upload? Refresh radio to which one? Original RUU-s don't work, they say error 155. Please help get my phone back to work! As previously I wanted to upload a 4.2 rom, this would be great to try one but right now it would be good enough to get it to work.
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 2011, 15:22:13
Please help!
AW: [Q] E/WifiStateMachine - Failed to load driver!
Have you been flashing the boot.img from the Rom every time after flashing a new Rom?
Fruite said:
Hi,
I have some problem with my desire s, hope someone can help me. I couldn't start any of the 4.2.2 roms (stuck at boot screen), so I tought that I have a hitachi panel. Unfortunately I didn't checked then, now I know that my desire s have a sony panel. Anyway, I have uploaded the mddi kernel after flashing a rom and it didn't helped. Then I was fed up with seeing roms trying to boot up so I decided to get back to a 4.0 rom or something.
This went well, I can boot up all of them but I don't have wifi at all! Logcat says the following when I try to enable wifi:
E/WifiStateMachine( 1614): Failed to load driver!
E/WifiStateMachine( 1614): DriverFailedState
Is there anything I can do? What kernel should I upload? Refresh radio to which one? Original RUU-s don't work, they say error 155. Please help get my phone back to work! As previously I wanted to upload a 4.2 rom, this would be great to try one but right now it would be good enough to get it to work.
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 2011, 15:22:13
Please help!
Click to expand...
Click to collapse
When attempting to flash RUU you must first relock bootloader,
Command (in fastboot )
fastboot oem lock
when done with RUU, in order to flash custom rom- you must unlock bootloader,
( you may use that same unlock_token you've used for unlocking the first time )
When you wish to use sense rom:
I recommend using kernel from amidabuddha
http://forum.xda-developers.com/showthread.php?t=1845039
Let see what you can do, with this info at hand
teadrinker said:
Have you been flashing the boot.img from the Rom every time after flashing a new Rom?
Click to expand...
Click to collapse
No. Should I?
Fruite said:
No. Should I?
Click to expand...
Click to collapse
OMFG. This was it. Wifi problem has been solved by just flashing boot.img from the rom. Thank you. Should I take a try with jb roms?
AW: [Q] E/WifiStateMachine - Failed to load driver!
Fruite said:
OMFG. This was it. Wifi problem has been solved by just flashing boot.img from the rom. Thank you. Should I take a try with jb roms?
Click to expand...
Click to collapse
Yes, you have a Sony panel, so go for it and try a jb Rom
Fruite said:
OMFG. This was it. Wifi problem has been solved by just flashing boot.img from the rom. Thank you. Should I take a try with jb roms?
Click to expand...
Click to collapse
Remember to flash the boot.img every time
"In the end, everything is a gag."
- Charlie Chaplin (1889-1977)
title says most of it, my current bootloader screen shows:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT 1.14.0002
TWRP 2.3.1.0
i rooted using the x-factor xploit maybe a week after it was released and haven't done any updates since as I have never run into any problems with that set up.
i've been using the CarbonROM nightly from 6/17 since the day it was released and haven't had any problems with it. here's a screenshot of the phone info which shows I am using the 3.4 kernel
View attachment 2106946
if i'm not having problems, would i be able to try out other 3.4 kernel roms? i've been avoiding taking a day to sit down and learn about adb/sdk and hope to achieve s-off as I have never used it/installed it. i read some noob guides earlier today and none of the links were working. any guides with working links? have I just been lucky?
Hi, its been almost a year since I flashed a ROM on my device, I'm currently on a Sense 5 ROM, ViperXL 4.2.0 to be exact, and its worked perfect and great and I saw no reason to switch to anything else. After a year though my phones been getting kinda laggy, and I mysteriously have very little Internal Storage, even after deleting almost every single app, I only get about 500mb to 800mb of free Internal Storage to install apps. So I'm looking to try flashing a new rom and starting fresh but I have forgotten alot of my knowledge on flashing and was seeking some help.
I want to try flashing the latest stable Cyanogenmod Build 10.2.1
I have a few questions before I do though,
1. Is it still necessary to downgrade the touchpanel firmware?
2. What version of TWRP do I need? I'm currently on v2.3.3.0 but after doing research, I found out there's new versions. Do I need 2.6.3.0 or 2.7.0.0?
3. Do I need to RUU or am I already good to go?
4. Can I flash the 4.4 Gapps or do I need to flash another version?
Here is my bootloader info:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-OFF RL
CID - 11111111
HBOOT - 2,15.0000
RADIO - 1.31a.32.45.16_2
OpenDSP - v33.1.0.45.1128
eMMC - boot
Aug 14 2013, 16:02:22:-1
Kinotsu said:
Hi, its been almost a year since I flashed a ROM on my device, I'm currently on a Sense 5 ROM, ViperXL 4.2.0 to be exact, and its worked perfect and great and I saw no reason to switch to anything else. After a year though my phones been getting kinda laggy, and I mysteriously have very little Internal Storage, even after deleting almost every single app, I only get about 500mb to 800mb of free Internal Storage to install apps. So I'm looking to try flashing a new rom and starting fresh but I have forgotten alot of my knowledge on flashing and was seeking some help.
I want to try flashing the latest stable Cyanogenmod Build 10.2.1
I have a few questions before I do though,
1. Is it still necessary to downgrade the touchpanel firmware?
2. What version of TWRP do I need? I'm currently on v2.3.3.0 but after doing research, I found out there's new versions. Do I need 2.6.3.0 or 2.7.0.0?
3. Do I need to RUU or am I already good to go?
4. Can I flash the 4.4 Gapps or do I need to flash another version?
Here is my bootloader info:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-OFF RL
CID - 11111111
HBOOT - 2,15.0000
RADIO - 1.31a.32.45.16_2
OpenDSP - v33.1.0.45.1128
eMMC - boot
Aug 14 2013, 16:02:22:-1
Click to expand...
Click to collapse
1) You don't need to downgrade your ts firmware.
2) You can use either of those versions you mentioned, some people have had issues with 2.7 not being able to mount the sd card though.
3) No need to RUU, your current firmware is fine.
4) You need to flash the appropriate gapps for whatever Android version the ROM is, you would only flash the 4.4 gapps if you're flashing a 4.4 ROM.
Is there any reason you're not flashing a KitKat ROM though? Support has ended for the lower Android versions now.
Sent from my Evita
Thank you! The only reason I don't want to use a Kitkat rom is because of stability, most I have seen are in beta or have known problems, I'm planning on using this as my daily driver and don't want to come across any issues.
If you're looking for stability, I flashed CM11 and ran it for a day or two, the only reason I flashed something else was a lack of features. I had no issues in the time I ran it.
Sent from my Evita
I've had a HTC One A9 (Sprint) for a week or so now, which belongs to my partner, carrier is unlocked, in the bootloader it was initially Locked, with S-On, since then it has been Unlocked and now Relocked.
She was paranoid about security and wanted me to try updating to the newest version, I naively attempted to do so with little knowledge and ended up soft-bricking the phone.
Its now stuck in a boot-loop and has no recovery.
I've spent an entire day trying to fix this myself, tried flashing various RUUs and everything error'd out or gave me signature errors, I basically can't seem to flash anything at all.
What should I be doing? I'm a little overwhelmed.
Kindly asking for some support from some more knowledgeable peeps, if you need any more info other than below, let me know, thanks
--------------------------------------------------------------------------------------------------------
*** Software status: Official ***
*** RELOCKED ***
*** S-ON ***
htc_hiaewhl PVT S-ON
LK-1.0.0.0000
[email protected]
OS-1.57.651.1
--------------------------------------------------------------------------------------------------------
Upon booting it says in pink at the bottom of the header section:
*** init fs_mgr_mount_all failed ***
Richi23 said:
I've had a HTC One A9 (Sprint) for a week or so now, which belongs to my partner, carrier is unlocked, in the bootloader it was initially Locked, with S-On, since then it has been Unlocked and now Relocked.
She was paranoid about security and wanted me to try updating to the newest version, I naively attempted to do so with little knowledge and ended up soft-bricking the phone.
Its now stuck in a boot-loop and has no recovery.
I've spent an entire day trying to fix this myself, tried flashing various RUUs and everything error'd out or gave me signature errors, I basically can't seem to flash anything at all.
What should I be doing? I'm a little overwhelmed.
Kindly asking for some support from some more knowledgeable peeps, if you need any more info other than below, let me know, thanks
--------------------------------------------------------------------------------------------------------
*** Software status: Official ***
*** RELOCKED ***
*** S-ON ***
htc_hiaewhl PVT S-ON
LK-1.0.0.0000
[email protected]
OS-1.57.651.1
--------------------------------------------------------------------------------------------------------
Upon booting it says in pink at the bottom of the header section:
*** init fs_mgr_mount_all failed ***
Click to expand...
Click to collapse
Have you tried the 1.57.651.1 RUU for Sprint?
Link: http://dl3.htc.com/application/RUU_HIA_AERO_WHL_M60_SENSE7GP_SPCS_MR_Sprint_WWE_1.57.651.1_R2.exe
Also, make sure you're in the proper mode. There's download and there's fastboot. You need a black background to use the RUU
Thanks so much John, all fixed!