Hello everyone,
I have SGS II (I9100) for about 2 years now. Im still on GB 2.3.4 KI4 (yeah dont ask why thats not my main issue here), rooted while ago with ZergRush exploit, and running HellCat's kernel. About two months ago, I fire up my phone and saw that I have no network. Went to About phone noticed that there is no baseband set, did *#06# and saw that my IMEI is empty. Luckily I had my EFS backed up with kTool, restored and was good to go. Today it happened to me again. Again restored with kTool and still good to go. So here is some facts regarding it, and I would like to know what might have causing it since I really dont update ROM's every 24 hours.
- 2 yearish old phone
- custom kernel with CWM
- did only one update from 2.3.2 (i think, cant recall what ROM was it shipped with) to 2.3.4
- didnt do factory reset after ROM upgrade
- happened before with soon-to-be-dead battery, but also with new one I got couple of days ago
- had running Dr.Web AV pretty much last year or so (I think only resident program running in background apart from loads of bloatware from Samsung)
Any info is more than welcomed since even I do have EFS backup, somehow I dont believe this is "expected behavior"...
Shall I (finally) upgrade to JB via Odin(Mobile Odin Pro?) and do factory reset/root after?
Can it be bad external card? Can internal memory can somehow be corrupted like hard drive with bad sectors or something? Really any info is more than welcomed.
Thank in advance
Here you go http://bit.ly/1bx9zPv
If you have actually read my post, before sending me to google, you would actually realized that I have EFS backup, and that I have recovered IMEI twice with kTool... Question is not HOW, but WHY. There is difference there. But hey, thanks for most ignorant reply you can actually think of. GZ you have just won the interwebs!
Hi,
i dont think its an hardware problem. I think that problem comes with your longtime running system und maybe that you didnt do a reset. Maybe you should finally upgrade to Jelly Bean - best way with Odin and a complete full wipe (save your data befor )
But keep cool, Jelly Bean looks very different to Gingerbread
Andi
andi2398 said:
Hi,
i dont think its an hardware problem. I think that problem comes with your longtime running system und maybe that you didnt do a reset. Maybe you should finally upgrade to Jelly Bean - best way with Odin and a complete full wipe (save your data befor )
But keep cool, Jelly Bean looks very different to Gingerbread
Andi
Click to expand...
Click to collapse
Thanks for the reply Andi. Actually I did that, and so far there is no issues with it (4.1.2). Did full wipe and so far all looking good, and I really like how it handles now. Still have EFS backup, just in case
Hi,
EFS Backup ist ever ever the first step after rooting don´t understand some guys who didnt do that or forget it.
Did you 4.1.2 root? If not, i recommed the philz kernel easy way, no triangle
have a nice day
Andi
andi2398 said:
Hi,
EFS Backup ist ever ever the first step after rooting don´t understand some guys who didnt do that or forget it.
Did you 4.1.2 root? If not, i recommed the philz kernel easy way, no triangle
have a nice day
Andi
Click to expand...
Click to collapse
Actually had some issues there... on 2.3.3 I had Hellcat kernel, wanted BLN, and some custom UOT Kitchen mods. Did full wipe from phone, and got it stucked in bootloop.
Let i a while, then said, **** it, and used Odin to flash 4.1.2 in from download mode. Stock ROM, so no binary counter issues. Started to boot up, showed me language selection and then crashed into bootloop... Assuming that it didnt finished wipe previously... Couldnt even got in into recovery (or was too stressed, but its 3 keys to press, dunno). Then, switched to download mode, flashed 4.0.3 that I had lying around, went to recovery, did wipe, and it booted up. Played with it, and in one point I said, "meh, Ill leave it on ICS"... Then something else said "You wuss! It took you 2 years to flash damn thing, and now you will stick to ICS?!?". Downloaded Mobile Odin Pro that I have purchased a while ago, flagged autoroot and flashed 4.1.2 from it. Again wiped it (just in case) and it booted up nicely. About 3 hours of stress, googling and browsing XDA Wife actually told my kid to stay away from me )
Then, wanted again BLN and thats the reason i skipped Philz and went for Siyah kernel instead. All nice and dandy so far *knock on the wood*
Still have EFS backup on numerous locations ofc
Cheers mate and thanks for participating
Related
Hi guys,
I've had an S2 for a few months now, and although I've managed to root the phone I'm still pretty green and need help.
I've had an OTA update from Gingerbread to ICS which I only installed as it popped up when I was using the phone.
The battery died earlier than expected and now it's stuck in a bootloop.
I don't want to have to ROM it as frankly I'm still in the "full theory" stage. I've heard of Odin and SamMobile.com, I've seen hours of vids on Youtube but I'm hoping there's another way to get around it. My confidence levels are improving but not there yet.
I have a Titanium backup on the phone from 2.3.4, if I wipe the phone from recovery will it work? Is there anything I can do apart from a new ROM?
If you had my lack of experience with this, what would you do? Thanks.
Can you get into download mode?
If so, you may have to bite the bullet and use Odin to flash the original firmware. You will be able to find it on these forums.
Don't sweat it, just download the Orange ICS ROM and put it in PDA on Odin and flash it, it'll take just a couple of minutes and you are done.
Thanks guys. It sounds so simple when you don't have a bootlocked phone to panic about.
FourQ said:
Thanks guys. It sounds so simple when you don't have a bootlocked phone to panic about.
Click to expand...
Click to collapse
Thats because it is simple! Ive never rooted because it looks confusing. But I've used odin many times to flash stock firmwares.
Sent from my GT-I9100 using XDA
Warren.D said:
Thats because it is simple! Ive never rooted because it looks confusing. But I've used odin many times to flash stock firmwares.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Nothing confusing about rooting either.
Download one of chainfires cfroot kernels or siyah kernel and flash via Odin.
That's it you're rooted.
----------------------
GTI9100
Hydra H2O 1.2.1
fluxi xx.01_rc5
if ya have a look around the forum, theres plenty of pre-rooted roms to flash via odin that wont increase ya binary counter, nothing hard about that.
Read the links in my signature
Sent from my GT-I9100 using XDA
I'm still reletively new to it
and I've had a couple of bootloops. A bit of a panic and then I figured out what I'd done wrong. As long as you follow instructions to the letter you'll be fine.
Edit: *Relatively, damn it.
Rooting it was easy enough. I went to unlockroot.com and a download later I was rooted. It's the ROMs that terrify me.
FourQ said:
Rooting it was easy enough. I went to unlockroot.com and a download later I was rooted. It's the ROMs that terrify me.
Click to expand...
Click to collapse
getting a custom rom isn't something you should be afraid of
getting a custom rom (or kernel) can improve your battery life (some of them).. but just be sure that getting a custom rom, it should be for whatever you're running (Gingerbread or ICS) usually, roms are flashable via CWM
take a leap, when you get into bootloop or get some problems along the process, just flash a stock firmware with odin..
@saywhatt
A mate (who's been doing this for years) has installed CWM7. It's odd how the things I liked about Gingerbread were added by Samsung, not Google.
I suspect I'll run with CWM7 for a week or so and decide then. First impressions aren't always correct (especially if you saw my face!) but after a week I should have a pretty good impression of the new ROM. I'm hesitant about ICS as the official version killed the phone but ultimately I may end up there.
It's good to watch the Youtube vids on how to flash stock ROMs with Odin. It's something I may try next week if CWM7 falls from favour.
Ultimately I'm sort of glad it happened. It's given me new confidence to try these things as I know there's a good chance it can all be recovered.
Q
I've never been too afraid of rooting or flashing. My first android device was a cheap piece of rubbish (an LG GTsomething i think), so I built up confidence in rooting and flashing because I didn't care if i damaged my phone.
I would recommend anyone who's not too confident to go out and get a cheap phone, it's a pretty significant investment but if your unsure about what your doing and just want to experiment, it's definitely worth the peace of mind.
...
I'm hesitant about ICS as the official version killed the phone
Click to expand...
Click to collapse
no m8 it didn't, your battery dying while you were updating killed your phone
It had finished a while before that. I was selecting a new font when it died.
You can't stuff up your phone anymore - its already in bootloop, what do you have to lose?
Odin is indeed very easy. Just make sure F.Partition is unchecked. Put the ROM in PDA and flash! Of course, after your phone has been put into download mode and connected to pc via usb and one of the Odin blocks have turned yellow.
Your phone is already rooted? If you made a backup in CWM (NOT Titanium Backup, this won't help you right now, as it's only for apps) you should restore that in CWM. A wipe and factory reset wouldn't help you right bow.
I understand you are a bit skeptic of ICS stock ROM right now, but remember you probably got pushed an early version,.the latest versions are very stable! Though Custom ROM's are the way to go eventually. Try the latest stable Cyanogen ROM.
Sent from my GT-I9100 using Tapatalk 2
@FreeStanler
Good point.
The stock ICS ROM was 4.0.3 if memory serves. It wasn't there for long but I was curious to see which version I'd been upgraded to.
I'm planning to see how this CWM7 ROM sits with me. If I can find out which app is causing this: http://t.co/9GfdXmD I'll probably be happy with it. I need to have a good play about with it to give it a fair chance. May end up with ICS/Stock ICS but for now we'll see how it goes.
Why on earth would you use Cm7 when Cm9 is far better, plus to flash a fw & then root with SuperOneClickRoot, or use the cf root kernel. The whole process takes 5 mins. Honestly M8 there's nothing to worry about. One thing I will say tho, Google Nandroid back up & once you know how to use etc, use it & make it your best friend coz that's the only thing that will fix the bootloop in the future
Sent from my GT-I9100 using xda premium
@blade30p
I didn't. A friend who's been doing this for years did it for me. I was hoping to get something resembling the stock Gingerbread on the phone, instead I got CWM7.
If anyone has the time i would like some help on how to flash my Note without bricking the phone. Reason i ask, is because i have already bricked it!! Sent it off to mobiletechvideos.com who unbricked it so now i'm back! I love the phone alot just hate stock rom and how slow it is. I would like to use a rom that is able to overclock? I've read about the sauron rom but i can't tell if it's out dated or if there is something better now?
I'm not a noob when it comes to rom's, Htc aria, samsung captivate, inspire, then the htc one x - i've all rom'd them but now i'm stump'd. The first go around, i flashed the rom and everything went thru fine. When i booted up the phone - Nothing changed!? so i find another rom, flashed it and the phone bricked. Tried jig everything else and to no avail. So 65$ later i'm back with the stock rom and it's rooted. Anyhow, here is the info i'm sure you guys are wanting to give me a hand!
Model Number
SAMSUNG-SGH-I717
Andriod Version
2.3.6
Baseband Version
I717UCLF6
Kernel Version
2.6.35.11
Build Number
GINGERBREAD.UCLA1
Cliff Notes -- Hard bricked trying to flash rom, Main goal want to overclock, battery life not issue. Please help flashing :angel:
do you have a custom recovery ? like cwm or the other one ( ive only had my note a week)
i would start with that..
If I were you (and I fully understand that I am not nor anyone else on here...) I would:
1. Install Samsung Kies and drivers to my laptop.
2. Start Samsung Kies and plug in the phone via USB cable.
3. Update the phone's OS via Kies to ICS. You won't brick it that way.
4. Give stock ICS a chance and if you still feel it's too slow for you (rolling eyes), flash a custom ROM/kernel.
nutpants said:
do you have a custom recovery ? like cwm or the other one ( ive only had my note a week)
i would start with that..
Click to expand...
Click to collapse
Yep, already have clockwork mod, That's no big deal.
BlackZenith said:
If I were you (and I fully understand that I am not nor anyone else on here...) I would:
1. Install Samsung Kies and drivers to my laptop.
2. Start Samsung Kies and plug in the phone via USB cable.
3. Update the phone's OS via Kies to ICS. You won't brick it that way.
4. Give stock ICS a chance and if you still feel it's too slow for you (rolling eyes), flash a custom ROM/kernel.
Click to expand...
Click to collapse
Sounds good sir i will give it a try - Meanwhile Anyone want to take a stab at walking me thru a rom that would work on my phone?
not that i have any idea what i am doing...
0 MAKE VERY SURE THE ROM YOU ARE FLASHING IS FOR YOUR PHONE... FORGET THE WORDS "note" or "galaxy" or anything else..
its the i717d or i 7100 or i 7000 that matters.. if in doubt dont do it..
1 download your cwm compatible rom (like blackstar or others) ( try to pick a recent rom no older than 2 months unless all the developers have jumped ship for the new phone)
( usually ends with a .zip) to your sd card)
2 use "android file verifier " ( from the market) to make sure your md5 hash of the download is prefect
( there SHOULD be a md5 someplace to verify the file download)
then by following info like whats found here.... http://forum.xda-developers.com/showthread.php?t=1584250 ( and that i copied and pasted)
boot into recovery by pressing volume up down,and power button at same time ( when your phone is turned off)
Select wipe data/factory reset and confirm
Select wipe cache partition and confirm
Select advanced - wipe dalvik cache and confirm
Select install zip from SD card
Select from internal SD card or wherever you placed it.
Select the ROM file and confirm.
rom will install
then AGAIN
Select wipe data/factory reset and confirm
Select wipe cache partition and confirm
Select advanced - wipe dalvik cache and confirm
boot up wait 5mins for it to boot.. dont touch it for 10 minutes after it boots
then
have fun..
dont forget to wonder if you bricked it during the first boot... that one takes the longest..
i have followed these directions drunk and sober when flashing over 20 times my new note i717d i got last week and im not bricked yet.
its the same system i used with my sgs2 i9100 for over a year and it still works..
but then dont think anything i have said here is right.
i could just be stupid and very lucky that i dont brick everything i touch but will not admit it.
READ A LOT, then READ more.. then ONE MORE TIME READ.. then flash.
BlackZenith said:
If I were you (and I fully understand that I am not nor anyone else on here...) I would:
1. Install Samsung Kies and drivers to my laptop.
2. Start Samsung Kies and plug in the phone via USB cable.
3. Update the phone's OS via Kies to ICS. You won't brick it that way.
4. Give stock ICS a chance and if you still feel it's too slow for you (rolling eyes), flash a custom ROM/kernel.
Click to expand...
Click to collapse
So after about 2 hours off and on, using different cables and google. No avail, UGH!
Samsung kies
Your device is not supported to update via samsung kies. Walked thru a few xda threads and they are saying update thru odin. Hell if i'm jumping ship to odin again, mine as well do a rom. I'm giving this 1 more shot, if it bricks i'll sell it lol!!
Mobiletechvideos most have had to do something extreme to repair your device, or they gave you one that.... never mind. Well, looks like you need to flash CWM and find a zip aligned ROM on here.
BlackZenith said:
Mobiletechvideos most have had to do something extreme to repair your device, or they gave you one that.... never mind. Well, looks like you need to flash CWM and find a zip aligned ROM on here.
Click to expand...
Click to collapse
LOL, no they did exactly what was promised. Even people who haven't bricked their device have ran into this issue!
Okay - After reading up and then watching a video on how to flash roms. Which looked exactly like what i had done before time and time again. I'm proud to say i'm ROM'D! I'm now running the blackstar rom and it's very zippy love it to death. Would like to have tried ICS 4.0.4 but took the plunge and happy with the turn out.
I've always came to this site for help but never made an account and you guys are too nice! Hopefully i can/could help someone else out down the road. Until then i'm going to enjoy not being so slow! Thanks!:good:
Its because you have a LF6 modem. Its not the modem that GB had. The Kies upgrade only works if your phone is stock.
You can use the kies emergancy firmware upgrade option.
Is not black star 4.04?
nutpants said:
Is not black star 4.04?
Click to expand...
Click to collapse
1st post says GB.
rangercaptain said:
1st post says GB.
Click to expand...
Click to collapse
First post here or first post of black star ?
written in your mud with my stick
Your first post.
The latest black star is based on the ics 4.0.4 firmware from Singapore
studacris said:
Your first post.
The latest black star is based on the ics 4.0.4 firmware from Singapore
Click to expand...
Click to collapse
The original Tom I started with was 2.3.6 since lies wouldn't let me update to ice 4.0.4 I jumped the gun and flashed blackstar. While it is a great rom. I'm thinking of trying more while I got my feet wet.
1Note said:
The original Tom I started with was 2.3.6 since lies wouldn't let me update to ice 4.0.4 I jumped the gun and flashed blackstar. While it is a great rom. I'm thinking of trying more while I got my feet wet.
Click to expand...
Click to collapse
I've been flashing two roms a day looking for something that supports total recall and underclocking, with a network mode menu that has lte on it.
I think I am out of luck.and I have forgotten some roms so I may flash everything again and keep notes...
It's research not an addiction.
written in your mud with my stick
Stage 1 of acceptance is denial
studacris said:
Stage 1 of acceptance is denial
Click to expand...
Click to collapse
LOL ...
And of course my favorite ....
"Trying is the first step toward failure ".....(Homer Simpson )...(grin )
Hello everyone. I'm a noob.
I have a Droid X2 and Verizon service. It was running Gingerbread 2.3.5 and version 1.3.418, and up until yesterday I hadn't even rooted it. I followed these instructions for CM10 carefully but apparently made a slight mistake.
I made sure to root properly: Superuser worked perfectly, I had Busybox, NANDroid, and Bootstrap Recovery all working, and the phone worked just like before.
In the tutorial I linked to above, I think I know where I went wrong. I downloaded GAPPS 4.2.2 (funky wording since he said 'latest' and then '4.1.x' , so not the latest) and then CM10 A3. I then went into BSR and installed from the external SD card. GAPPS succeeded, but CM10 did not (Status 7, some kernel disapproval or something). When I booted the phone after that, MultiTouch keyboard couldn't start and so I just froze it with Titanium Backup and used Swype because it was annoying. The next thing I tried came from another xda thread (that I seem to have misplaced) saying that removing the top 2 lines of META-INF/com/google/android/updater-script would make it work. I'm pretty sure this failed similarly to before. I then tried wiping all data (since I had backed it up 3 different ways) and installing CM10. It still didn't work, and when I booted I got to my current state of purgatory.
Now when I boot, it tries to run the initial setup but that crashes (and multitouch keyboard crashes too). I've probably lost root access and currently don't have Titanium Backup or any other method to restore from backup since the programs were wiped. I've been trying to do an SBK factory reset using RSD Lite, but the phone won't go into RSD mode.
At this point I just want a working phone again and I'm not sure what to do.
TL;DR: Used the wrong GAPPS version when installing CM10 A3, decided to wipe all my data and try the install, now I'm stuck in neutral.
I guess the internet lied and gave me the wrong SBK the first time. Setup did work, and it wasn't RSD like I had thought.
I still would like to know what went wrong the first time through, and why it seemed like I wasn't able to overwrite the incorrect GAPPS version I had first installed. Once I saw my mistake I did use the correct version and nothing changed.
Dasoccerguy said:
I guess the internet lied and gave me the wrong SBK the first time. Setup did work, and it wasn't RSD like I had thought.
I still would like to know what went wrong the first time through, and why it seemed like I wasn't able to overwrite the incorrect GAPPS version I had first installed. Once I saw my mistake I did use the correct version and nothing changed.
Click to expand...
Click to collapse
Did you get it working then? Were you running A2 before hand?
Dasoccerguy said:
Hello everyone. I'm a noob.
I have a Droid X2 and Verizon service. It was running Gingerbread 2.3.5 and version 1.3.418, and up until yesterday I hadn't even rooted it. I followed these instructions for CM10 carefully but apparently made a slight mistake.
I made sure to root properly: Superuser worked perfectly, I had Busybox, NANDroid, and Bootstrap Recovery all working, and the phone worked just like before.
In the tutorial I linked to above, I think I know where I went wrong. I downloaded GAPPS 4.2.2 (funky wording since he said 'latest' and then '4.1.x' , so not the latest) and then CM10 A3. I then went into BSR and installed from the external SD card. GAPPS succeeded, but CM10 did not (Status 7, some kernel disapproval or something). When I booted the phone after that, MultiTouch keyboard couldn't start and so I just froze it with Titanium Backup and used Swype because it was annoying. The next thing I tried came from another xda thread (that I seem to have misplaced) saying that removing the top 2 lines of META-INF/com/google/android/updater-script would make it work. I'm pretty sure this failed similarly to before. I then tried wiping all data (since I had backed it up 3 different ways) and installing CM10. It still didn't work, and when I booted I got to my current state of purgatory.
Now when I boot, it tries to run the initial setup but that crashes (and multitouch keyboard crashes too). I've probably lost root access and currently don't have Titanium Backup or any other method to restore from backup since the programs were wiped. I've been trying to do an SBK factory reset using RSD Lite, but the phone won't go into RSD mode.
At this point I just want a working phone again and I'm not sure what to do.
TL;DR: Used the wrong GAPPS version when installing CM10 A3, decided to wipe all my data and try the install, now I'm stuck in neutral.
Click to expand...
Click to collapse
you state in the beginning that you are on 2.3.5. it is crazy that you were even able to flash cm10. it is made for 2.3.4 . and DZKs OP on cm10 is a bit sketchy in the wording and severly outdated.
there are a few things you need to do in order to get BSR working inside of A3 , as well as needing the GAPPS for 4.1.X and not 4.2.2 this is only cm10 , not 10.1 .
you need to SBF back to 2.3.4 (google EZsbf for droid x2) it is way easier than trying to use rsdlite for a "noob" , and then root. then follow the steps you completed to get where you are now, except use the right gapps.
THEN: (this is not in the OP for cm10 ) , perform THIS : http://forum.xda-developers.com/showpost.php?p=37698274&postcount=1573 in order to get the patched cm7 bootstrap working. DO NOT try to use the regular BSR .
i can try to help as i get back to my computer here and there, but hopefully others pitch in , as i dont have that much time. hope this helped.
Simpsons11 said:
Did you get it working then? Were you running A2 before hand?
Click to expand...
Click to collapse
I got back to 2.3.5 and restored all my apps and data, so I called it a night. Well... the sun had come up, but same idea. Like I said, up until yesterday I had yet to even root the phone, so I was just running the stock version of Android given to me by Verizon.
Lorenzo VonMatterhorn said:
you state in the beginning that you are on 2.3.5. it is crazy that you were even able to flash cm10. it is made for 2.3.4 . and DZKs OP on cm10 is a bit sketchy in the wording and severly outdated.
there are a few things you need to do in order to get BSR working inside of A3 , as well as needing the GAPPS for 4.1.X and not 4.2.2 this is only cm10 , not 10.1 .
you need to SBF back to 2.3.4 (google EZsbf for droid x2) it is way easier than trying to use rsdlite for a "noob" , and then root. then follow the steps you completed to get where you are now, except use the right gapps.
THEN: (this is not in the OP for cm10 ) , perform THIS : http://forum.xda-developers.com/showpost.php?p=37698274&postcount=1573 in order to get the patched cm7 bootstrap working. DO NOT try to use the regular BSR .
i can try to help as i get back to my computer here and there, but hopefully others pitch in , as i dont have that much time. hope this helped.
Click to expand...
Click to collapse
I wasn't able to flash CM10. I was able to flash GAPPS 4.2.2, but then unable to flash GAPPS 4.1.x over that installation.
And is it really that outdated and sketchy? The version of CM10 I was trying to flash was made on January 11, 2013. Correct me if I'm wrong, but Gingerbread 2.3.5 is almost 2 years old now, right? It's surprising that I'd have to go back to the previous version.
I may try out your suggestions later, but 8 hours of fiddling with my phone yesterday wore me out a little (a lot). Thanks!
Dasoccerguy said:
I got back to 2.3.5 and restored all my apps and data, so I called it a night. Well... the sun had come up, but same idea. Like I said, up until yesterday I had yet to even root the phone, so I was just running the stock version of Android given to me by Verizon.
I wasn't able to flash CM10. I was able to flash GAPPS 4.2.2, but then unable to flash GAPPS 4.1.x over that installation.
And is it really that outdated and sketchy? The version of CM10 I was trying to flash was made on January 11, 2013. Correct me if I'm wrong, but Gingerbread 2.3.5 is almost 2 years old now, right? It's surprising that I'd have to go back to the previous version.
I may try out your suggestions later, but 8 hours of fiddling with my phone yesterday wore me out a little (a lot). Thanks!
Click to expand...
Click to collapse
the OP for cm10 hasnt really been updated since alpha 1 . so yeah it is outdated. alpha 2 had a non working wifi module that was never even mentioned in the OP and had to be figured out by the droid x2 community. alpha 3 had the working wifi back in, but did not have the proper Hijack.zip in place in the system files, whereas the old versions did. this was also never mentioned in the OP.
watch this video. it may help.
http://www.youtube.com/watch?v=HJdvyufvYp0
the dude who made this video also has DOZENS of how-to videos for the droid x2 on his channel. just search for it on youtube. (ex: how to sbf droid x2)
sbfing your phone to 2.3.4 , using EZSBF , shouldnt take more than 15 minutes.
2.3.5 re-introduced a lot of issues that we had with 2.3.4, so most devs base their roms around 2.3.4. in fact, there are really only two roms for 2.3.5 worth trying out, Eclipse, and gingerbread phone , 7 and they are both gingerbread. :crying:
if you read up on what needs to be done, the whole process of SBF, ROOT, and flash cm10 THEN gapps, should all take less than an hour, even for someone who is fairly inexperienced.
i wasnt trying to dog DZK's post for cm10. i was only stating that if you follow HIS instructions, it is confusing as hell.
Lorenzo VonMatterhorn said:
the OP for cm10 hasnt really been updated since alpha 1 . so yeah it is outdated. alpha 2 had a non working wifi module that was never even mentioned in the OP and had to be figured out by the droid x2 community. alpha 3 had the working wifi back in, but did not have the proper Hijack.zip in place in the system files, whereas the old versions did. this was also never mentioned in the OP.
watch this video. it may help.
youtubelink
the dude who made this video also has DOZENS of how-to videos for the droid x2 on his channel. just search for it on youtube. (ex: how to sbf droid x2)
sbfing your phone to 2.3.4 , using EZSBF , shouldnt take more than 15 minutes.
2.3.5 re-introduced a lot of issues that we had with 2.3.4, so most devs base their roms around 2.3.4. in fact, there are really only two roms for 2.3.5 worth trying out, Eclipse, and gingerbread phone , 7 and they are both gingerbread. :crying:
if you read up on what needs to be done, the whole process of SBF, ROOT, and flash cm10 THEN gapps, should all take less than an hour, even for someone who is fairly inexperienced.
i wasnt trying to dog DZK's post for cm10. i was only stating that if you follow HIS instructions, it is confusing as hell.
Click to expand...
Click to collapse
Thanks for the link. I remember watching one of his videos yesterday for something, but apparently this was the one I needed! He does have another video on how to SBF back to 2.3.4, so I think I will just go for it right now.
Also yesterday it only took so long because I had to figure out what mess I had gotten myself into before I could figure out how to figure out what to do. This definitely looks like it shouldn't take more than an hour. :good:
I do have one quick question about backups. NANDroid is a full system backup, including the OS, right? And Titanium Backup is for apps and data? Therefore I should be able to restore all of my apps and data into Android 4.2.1 with Titanium, right? I at least know how to get back to 2.3.5 and restore my data if I can't restore it in 4.2.1, but I'd rather not have to go through this process again if I find out that Titanium can't restore everything.
(haha... I couldn't quote you because of the outside link and my 'xda noob' status )
Dasoccerguy said:
Thanks for the link. I remember watching one of his videos yesterday for something, but apparently this was the one I needed! He does have another video on how to SBF back to 2.3.4, so I think I will just go for it right now.
Also yesterday it only took so long because I had to figure out what mess I had gotten myself into before I could figure out how to figure out what to do. This definitely looks like it shouldn't take more than an hour. :good:
I do have one quick question about backups. NANDroid is a full system backup, including the OS, right? And Titanium Backup is for apps and data? Therefore I should be able to restore all of my apps and data into Android 4.2.1 with Titanium, right? I at least know how to get back to 2.3.5 and restore my data if I can't restore it in 4.2.1, but I'd rather not have to go through this process again if I find out that Titanium can't restore everything.
(haha... I couldn't quote you because of the outside link and my 'xda noob' status )
Click to expand...
Click to collapse
a nandroid backs up the OS as well as all apps and data, but that only helps you if you are modding/messing with that specific rom. so yes, TB is the way to go for restoring apps across roms. glad to point you in the right direction! report back once youve made the jump. :fingers-crossed:
Success!
I used Tomsgt123's tutorials and they were fantastic. First I had to install the 2.3.4 SBK and then CM10 and Gapps. I'm currently running Titanium Backup and it's working flawlessly.
I did have one hiccup earlier though. I noticed that my contacts weren't backed up, and apparently I had disabled the online contact backup also. I was hoping that I could do a NANDroid restore, backup my contacts, and then go through with the CyanogenMod installation. But, the restore kept hanging and refused to finish. I tried 3 or 4 times, and on the last try I restored by section and it was the data section that caused the hang.
So, I'll have to rebuild my contacts list a little bit, but since SMS was backed up I'll at least get the people I care about . Cyanogen is pretty sleek and so far it's been noticeably faster than Gingerbread. I was constantly getting a low framerate just navigating my mainscreen before, and that's one of the reasons I was inspired to try out Jellybean or just anything newer. I can't make any claims about battery life yet since I haven't unplugged it, but other reviews said the battery can last more than twice as long which is fantastic.
I can't thank you enough, Lorenzo, for pointing me in the right direction. :highfive:
Dasoccerguy said:
Success!
I used Tomsgt123's tutorials and they were fantastic. First I had to install the 2.3.4 SBK and then CM10 and Gapps. I'm currently running Titanium Backup and it's working flawlessly.
I did have one hiccup earlier though. I noticed that my contacts weren't backed up, and apparently I had disabled the online contact backup also. I was hoping that I could do a NANDroid restore, backup my contacts, and then go through with the CyanogenMod installation. But, the restore kept hanging and refused to finish. I tried 3 or 4 times, and on the last try I restored by section and it was the data section that caused the hang.
So, I'll have to rebuild my contacts list a little bit, but since SMS was backed up I'll at least get the people I care about . Cyanogen is pretty sleek and so far it's been noticeably faster than Gingerbread. I was constantly getting a low framerate just navigating my mainscreen before, and that's one of the reasons I was inspired to try out Jellybean or just anything newer. I can't make any claims about battery life yet since I haven't unplugged it, but other reviews said the battery can last more than twice as long which is fantastic.
I can't thank you enough, Lorenzo, for pointing me in the right direction. :highfive:
Click to expand...
Click to collapse
thats awesome. i loved the feeling when i first flashed a new rom on this phone. glad you got it figured out. make sure to thank Tomsgt for his videos as well . hes a cool dude and put a lot of time into it.
as for battery life, its kinda a bit rough on cm10. i wouldnt say twice as good. that would be too good to be true...lol . but if you limit your apps, it shouldnt be that much worse.
one thing, to improve performance, under settings, go to developer options, and near the bottom there is background processes. its set at standard limit by default. change it to three at most. this will make a noticeable improvement in performance, but will also need to be re-set at 3 at most if you ever reboot/power off.
glad i could help! :highfive:
Hey y'all.
So many threads ago I posted up on how to root a SGS2 I900P, which in the end I did no problems. The ONLY problem I encounted where I'd flash a different ROM and wanted to restore back to my factory loaded Orange UK rom, which when I restored it with no problems it just went through the 'boot loop' phase. I read up that this is caused due to a faulty emmc 'bricking bug' and luckily it was only "soft bricked".
Cut the long story short I managed to re-flash the Orange (UK) carrier firmware (after many USB cable changes and port swaps and fails) via Odin and retain my previously installed apps and so on and had to re-root. Is there a method or some sort of fix for the emmc bug issue for future wipes/restores ?
Something new I learnt in all that process too,
muffintastic said:
Hey y'all.
So many threads ago I posted up on how to root a SGS2 I900P, which in the end I did no problems. The ONLY problem I encounted where I'd flash a different ROM and wanted to restore back to my factory loaded Orange UK rom, which when I restored it with no problems it just went through the 'boot loop' phase. I read up that this is caused due to a faulty emmc 'bricking bug' and luckily it was only "soft bricked".
Cut the long story short I managed to re-flash the Orange (UK) carrier firmware (after many USB cable changes and port swaps and fails) via Odin and retain my previously installed apps and so on and had to re-root. Is there a method or some sort of fix for the emmc bug issue for future wipes/restores ?
Something new I learnt in all that process too,
Click to expand...
Click to collapse
To avoid brickbug is by flashing JB 4.1.2. (good alternative!)
But if you really like ICS then i suggest you move back to 4.0.3. There is no avoiding brickbug on 4.0.4.
If you have rooted it, you can check with 'Brickbug check' app on google play, to see if you have sane (or insane) chip (brickbug or not), cause most custom kernels and roms have found a solution to this bug, and use it on their roms/kernels. Which means on those you can safely wipe and restore etc.. (but check brickbug app first on google play)
Yep. Don't wipe a rooted phone running 4.0.4. And if you're really paranoid, don't even wipe a non-rooted phone running 4.0.4 (Entropy mentioned at least one case he knew of where someone borked their phone doing a wipe on a phone running 4.0.4 via stock Android recovery, tho it seems to be very rare).
The TL;DR is don't run rooted stock 4.0.4 if you mess with your phone in any way.
I know that's not a fix, but that's because there isn't one. Some chips aren't susceptible to the bug; there's an app floating around here somewhere/Google Play where you can check which chip you have (seems to be more that are susceptible).
Your 1st paragraph is a load of crap.Bootloop has nothing to do with "brickbug".More like by you not running kernel cleaning script,or not factory resetting before/after flashing a new rom.
As mentioned by others,just dont have 4.0.4 running on your phone.So you are still left with over 100 custom/stock roms to choose from........lol
Was the backup of JB? Or ICS? OP doesn't say. If it was JB, I'd be willing to bet that the bootloop was due to an attempt to restore the stock rom, but without restoring preload.
Sent from a galaxy far, far away
Hopper8 said:
Was the backup of JB? Or ICS? OP doesn't say. If it was JB, I'd be willing to bet that the bootloop was due to an attempt to restore the stock rom, but without restoring preload.
Sent from a galaxy far, far away
Click to expand...
Click to collapse
Im not sure Hopper.I am leaning towards the restore would be "cancelled" due to not being complete,rather than it succeeding leading to bootloop.
But hes not said.
And he cant get "factory" rom with a restore as it didnt come with cwm lol.
Sorry to clear things up.. I updated it to 4.1.2 via Kies many months ago. I used PhilZ method to root, no problem. Few months down the line since then I put LiquidSmooth 2.4 (few days ago) then restored a backup from PhilZ recovery and put 4.1.2 and everything back on no problem. Then restarted the phone and it when into a boot loop of the Orange and Samsung logo.
I'm not stupid as I've rooted my own SGS3 and Samsung Galaxy ACEs etc, Just forgotten to put that info in lol and yes I always use the Factory Reset to install a new rom.
And yes when I managed to get it restored from this so called boot loop (by putting 4.1.2 Orange UK firmeware back on via Odin) the EMMC brick bug is present as i've checked via an app via Google Play. My overall goal is to eliminate this problem or temp fix so I can put different roms on and if I don't like them recovery back to the latest restore without issues.
Are we on the same line now ?
And as we've said, you can't eliminate the problem. You can avoid the problem by not running 4.0.4 stock roms. It's really quite simple, but like a lot of people here you're trying to make it complex when there's no need to.
help me out here please
MistahBungle said:
And as we've said, you can't eliminate the problem. You can avoid the problem by not running 4.0.4 stock roms. It's really quite simple, but like a lot of people here you're trying to make it complex when there's no need to.
Click to expand...
Click to collapse
ok its a long story so i better get started... my friend had his phone rooted and installed a jelly bean version of Paranoid android and he wanted to put kitkat on it, he downloaded the cm11 latest nightly and told me to flash it i proceed to flash the phone but it failed and showed me "error status 7" so the phone couldnt get neither into the previous pa nor in the cm11... after some research and messing with the META INF stuff to sol the status 7 thing i found out that the problem was that he wasnt using a kitkat compatible recovery... i installled it and finally got to flash cm11.. that didnt came out as you may thought the phone showed it had -15246384352 % of battery made a freking glitch when the sreen rotated and it wouldnt recognize either of the sd cards (internal memory or external sd card) so i couldnt flash it again, wipe data/cache wouldnt solve the problem either... i turn into our ol friend odin and flashed stock JB wich worked perfectly except that i had the same issue with the memories... used philz to root the phone again, the try to format /system /data /emmc to check if that was the problem annnnd ta da the phone wont boot :silly: odin keeps failing to flash stock again and i dont jknow what to do....
sorry for the long post but i guess that you might need alll the info you could get for helping me...
thanks a lot
andreshbozo said:
ok its a long story so i better get started... my friend had his phone rooted and installed a jelly bean version of Paranoid android and he wanted to put kitkat on it, he downloaded the cm11 latest nightly and told me to flash it i proceed to flash the phone but it failed and showed me "error status 7" so the phone couldnt get neither into the previous pa nor in the cm11... after some research and messing with the META INF stuff to sol the status 7 thing i found out that the problem was that he wasnt using a kitkat compatible recovery... i installled it and finally got to flash cm11.. that didnt came out as you may thought the phone showed it had -15246384352 % of battery made a freking glitch when the sreen rotated and it wouldnt recognize either of the sd cards (internal memory or external sd card) so i couldnt flash it again, wipe data/cache wouldnt solve the problem either... i turn into our ol friend odin and flashed stock JB wich worked perfectly except that i had the same issue with the memories... used philz to root the phone again, the try to format /system /data /emmc to check if that was the problem annnnd ta da the phone wont boot :silly: odin keeps failing to flash stock again and i dont jknow what to do....
sorry for the long post but i guess that you might need alll the info you could get for helping me...
thanks a lot
Click to expand...
Click to collapse
Here is my situation.
I had 4.1.2 JB. Installed CM11 M8 and CWM_6.0.4.7(coming previously from Siyah) at the end of July. In the beginning of October my phone just shut down. That happened before on the same and previous rom so I wasn't worried. I turned it on and phone was in bootloop. That was strange because the last time that happened I installed Chainfire. So bootloop without any cause..that was strange. I tried making a backup before flashing the ROM. But I got an error. I can't remember but I can dig it somewhere if you want it. I tried then flashing recovery(bad idea) and Odin again reported an error. When I restarted phone I noticed that my Recovery mode was gone. Just gone and with no solution on how to restore it. I tried numerous methods OMAP drivers, heimdall, .pit file method but nothing. So I brought my sgs2 to the store where I bought it and they concluded that it was bad eMMC chip.
Now, your problem reminds me of mine because Odin wouldn't want to flash anything without an error(well, not exactly anything, I managed to flash some partition using Heimdall but it was not sufficient) but it doesn't have to be.
What version of cwm were you using?
Ok, so looks like my phone decided to take some time off...
What happened was that yesterday I was playing a game on it and the battery had just about 3% left, so I put it to charge (wall charger) and the game froze.. Din't pay too much attention to it when I came back a couple of hours later, the phone was off. Turned it on and didn't go past the Samsung logo.... And it's been like this since then.
I was running a 4.4.4 ROM Eclipse V5 By AC, which was working fine and I have access to TRWP Recovery and also to Download Mode.
I have tried to restore a different nandroid backups and install other ROMS, inclusively an original stock ROM.. I tried to restore EFS, but only managed to restore and old one that was stored in the phone's memory.
I also have an emergency firmware and a stock one and I believe I have everything else to be able to do it by Odin, but I don't have USB debug!!!
Please tell me there is a "magical way" to enable USB debugging without having access to the phone!! Even on Download Mode, Odin doesn't recognize the phone. I also have Samsung and ADB drivers installed.
I'm getting desperate and don't know what else can I do to sort this out..
My phone is GT-I9300 International, running a 4.4.4 ROM (when it bricked) and have PhilZ Touch 6.48.4
Any ideas or suggestions, please???? Thanks guys!
Deinstall all Samsungdrivers, KIES and Odin on PC. Install actual software from sammobile.com. Try another USB-port, if possible at mainboard. Run Odin as Admin. If phone isn't shown in Odin, it's gone.
Hey rp158, thanks for your reply! I'll try and do that! Hope I don't have to bury it ......
migasbr said:
Hey rp158, thanks for your reply! I'll try and do that! Hope I don't have to bury it ......
Click to expand...
Click to collapse
*EDIT*
Thanks again for your advice rp158! I decided to borrow a laptop running Windows 7 (I have Windows 10 on my PC), installed fresh version of Kies and finally I got it to work with Odin!! Flashed a couple of emergency firmware and finally an original 4.3 ROM. The problem continued and finally I flashed an efs fix. I guess that did the trick and my phone came back from the dead! Rooted my phone again, installed PhilZ and restored a previous backup I had.
Now I still have one problem to solve! I still didn't managed to have network service... I already managed to fix my IMEI, or at least when I press*#06#, shows the right IMEI, but no network service....
I read about a few "fixes" for this but I haven't fully tried any of them.. Any suggestions?...
Thanks again for your help!
Maybe, you imported wrong settings by restoring backup. So go back to firmware again without any patches and check, whether IMEI and net access are ok. If not, try KIES-emergency-repair. If you succeed, don't use your backup (and continue with TWRP ).
rp158 said:
Maybe, you imported wrong settings by restoring backup. So go back to firmware again without any patches and check, whether IMEI and net access are ok. If not, try KIES-emergency-repair. If you succeed, don't use your backup (and continue with TWRP ).
Click to expand...
Click to collapse
Hi rp158, I've reinstalled the original firmare and ROM by Kies and everything went well but I was still getting a "0049" IMEI... I was burning my eyes so much because of it that I decided to take the phone to a store. They have been trying to re-register the IMEI for the last couple of days and just got a message saying that they have managed to do it. I'l pick it up tomorrow. If they really managed, it will cost me about 25 Euros, but will sabe a lot eye burning! :silly:
First I'll do is a Nandroid job and about 100 EFS backups! lol
It shouldn't be problem to restore a previous backup that I know it's working well, right?...
Maybe. Or a goed moment to try something fresh...
rp158 said:
Maybe. Or a goed moment to try something fresh...
Click to expand...
Click to collapse
Hello rp158, they actually did it!! Phone works great and it's totally functional. Tried to find out what kind of software they used but they wouldn't tell me as expected..
Made a nandroid and efs backup straight away and restored my previous ROM, just to do a Titanium backup of everything and now I', using a 5.1 ROM.
Thanks again for your help!
@migasbr: fine.