Related
Hello all,
I have accidently flashed my nexus s with a 4G rom... I know stupid me.
Now I cannot get service and baseband .
I cannot seem to fix it. Does somebody have a tip? I hope so cuz I dont wanna be buying a new phoney.
Thnx in advance!
Just restore a backup on the recovery. Or, if you didn't do a backup (please tell me i'm wrong), download the right ROM, copy it to your phone, WIPE everything and flash it
Well I tried that but the backup gives an MD5 error . And I cannot find a clean rom I do need now. All the ones I tried gave an error in CWM error 7 or something.
Tokageroh said:
Well I tried that but the backup gives an MD5 error . And I cannot find a clean rom I do need now. All the ones I tried gave an error in CWM error 7 or something.
Click to expand...
Click to collapse
I see. Well, your backup is corrupted, we can't do anything for it.
But, go to your Nexus S section in XDA, download one and see if the MD5 match. Then if it's ok, try to flash it : )
FYI, i don't have a nexus, so, i'm not a professional of it but... a rom for a 4G phone if you only have a 3G phone will boot up normally but give problem with GSM and data connection. So that's weird.
Try again with a ROM that you download now and match the MD5. And then, if error still here, we must a Nexus S owner to help you
I will try so when i get back from work. I really hope I can get it to work. The phone boots normally but wont ask for my pin and that stuff. How do I check the MD5 if I may ask?
Tokageroh said:
I will try so when i get back from work. I really hope I can get it to work. The phone boots normally but wont ask for my pin and that stuff. How do I check the MD5 if I may ask?
Click to expand...
Click to collapse
http://www.commentcamarche.net/download/telecharger-34058173-md5-checksum with this programm for windows.
You put the rom in, it shows the MD5. Then look on the topic where you downloaded the ROM and see if it's the same. If md5 is not written in the topic, ask for it
Also I forgot to mention that when I tried to flash to a NS mod i got an error 7 or something in CWM
Hello,
After I rooted my ATT galaxy note ICS 4.0.4, downloaded the blackstar6, put it in my sdcard in the phone. Wiped all the data etc...as instructed, when it got to the flashing part, can't open /sdcard/blackstar_VI.zip (bad). I tried 3 times, then restored the back up, then re-do again. still the same problem...any help would be appreciated. Thanks
naomile said:
Hello,
After I rooted my ATT galaxy note ICS 4.0.4, downloaded the blackstar6, put it in my sdcard in the phone. Wiped all the data etc...as instructed, when it got to the flashing part, can't open /sdcard/blackstar_VI.zip (bad). I tried 3 times, then restored the back up, then re-do again. still the same problem...any help would be appreciated. Thanks
Click to expand...
Click to collapse
Try redownloading black star and try again.
a3plew said:
Try redownloading black star and try again.
Click to expand...
Click to collapse
I did try, still the same result Thanks for responding.
You didn't mention how you are flashing BS6. Are you using CWM or TWRP?
rangercaptain said:
You didn't mention how you are flashing BS6. Are you using CWM or TWRP?
Click to expand...
Click to collapse
sorry, CWM, Thanks
Well if you entered CWM recovery, wiped caches, did a factory reset, then flashed BS6, and you are not getting the rom to boot, the file is corrupted. It happens from time to time.
rangercaptain said:
Well if you entered CWM recovery, wiped caches, did a factory reset, then flashed BS6, and you are not getting the rom to boot, the file is corrupted. It happens from time to time.
Click to expand...
Click to collapse
well, I downloaded bs6 at 2 different links, what should I do next. This is my first android phone sorry for some noobs questions.
naomile said:
well, I downloaded bs6 at 2 different links, what should I do next. This is my first android phone sorry for some noobs questions.
Click to expand...
Click to collapse
Did you check MD5 and make sure they match? Like Ranger said, its probably a corrupted file.
and-on-ROIDS said:
Did you check MD5 and make sure they match? Like Ranger said, its probably a corrupted file.
Click to expand...
Click to collapse
hix I don't know how to do that, and where to check. Show me plizzzzzzzzzzzz
How are you entering recovery?
rangercaptain said:
How are you entering recovery?
Click to expand...
Click to collapse
hold down the volume up and down and power buttons at the same time. I got to the part that installing the bs6, then it said can't open bs6 (bad), so I have to do the restore. I just don't understand what the problem is ?
you didn't unzip the file, right?
rangercaptain said:
you didn't unzip the file, right?
Click to expand...
Click to collapse
ofcourse not sir, I followed instructions step by step.
Well try another rom and see if you get the same error message.
What's the word? Were you able to flash another rom?
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
bigfau said:
What's the word? Were you able to flash another rom?
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
No sir, I was not able to flash the bs6, it just aborted. would you help? thanks
Try flashing another another rom Its either a recovery issue, rom download issue, operator issue.
hix, CWM ofcourse otherwise how can I flash the ROM? anyway, just tried different ROM ICS IMM76D UCLF6 Base Build #4 samething happended I really don't know what's the problem. REALY need help urgently. Pleaseeeeeeeee help me
Either your recovery is broken or you are missing a step/detail. How did you install CWM? Did you use Odin and flash a kernel or did you use Rom Manager app? Because the app doesn't work.
rangercaptain said:
Either your recovery is broken or you are missing a step/detail. How did you install CWM? Did you use Odin and flash a kernel or did you use Rom Manager app? Because the app doesn't work.
Click to expand...
Click to collapse
I used odin to flash. I had superuser I guess that means my device is rooted. then I downloaded the bsROM and other cooked ROM. I copied the bsROM zip to my sd card, CWM to recovery then wiped out all the data as instructed, then installed the ROM, everything went fine to this part then it couldnot open then aborted. tried 3,4 times with different rom: same results, aborted.
INFO:
Model:Galaxy siii gt-i9300
ROM: Android Revolution HD 17.1
Kernel:Perseus 28.2
I installed ARHD 17.1 and I noticed that my phone wasnt so smooth as it was with v15.2.So I booted into cwm 6.0.1.2 and flashed v15.2.Then I flashed ROM CLEANER.Everything was fine till I tried to reboot my phone.It stuck at samsung logo.I know that this is a constant problem here but I ve done a lot of research and didnt find exact instructions of what to do.I tried to flash CWM recovery once again with Odin.Unfortunatelly it stuck again but this time at Samsung GT-I9300 screen.Please help me if you can.Any help would be apprecieated.
P.T.J0hnnie said:
INFO:
Model:Galaxy siii gt-i9300
ROM: Android Revolution HD 17.1
Kernel:Perseus 28.2
I installed ARHD 17.1 and I noticed that my phone wasnt so smooth as it was with v15.2.So I booted into cwm 6.0.1.2 and flashed v15.2.Then I flashed ROM CLEANER.Everything was fine till I tried to reboot my phone.It stuck at samsung logo.I know that this is a constant problem here but I ve done a lot of research and didnt find exact instructions of what to do.I tried to flash CWM recovery once again with Odin.Unfortunatelly it stuck again but this time at Samsung GT-I9300 screen.Please help me if you can.Any help would be apprecieated.
Click to expand...
Click to collapse
just a little suggestion here:
can u still enter recovery mode? if yes, try to clean everything first(dalvic cache..) see if the problem is solved or not...
if not..u will need to reflash new rom and start all over again
jeffreydesiree said:
just a little suggestion here:
can u still enter recovery mode? if yes, try to clean everything first(dalvic cache..) see if the problem is solved or not...
if not..u will need to reflash new rom and start all over again
Click to expand...
Click to collapse
The thing with recovery mod is weird.Sometimes I can,sometimes I cannot.But when I can,it can only be a previous version of 6.0.1.2 flashed with odin and not 6.0.1.2.Right now I m trying and I cant get into recovery.I searched the official jellybean 4.1.1 for my country (greece) but cant find it and dont know what to do.:/
hi!
perhaps you had a bad download of V17.1? you may try checking the md5 sum....
i suggest you do a clean install, flash the superwipe for arhd which is found in the OP, and then flash arhd again
regards,
saywhatt said:
hi!
perhaps you had a bad download of V17.1? you may try checking the md5 sum....
i suggest you do a clean install, flash the superwipe for arhd which is found in the OP, and then flash arhd again
regards,
Click to expand...
Click to collapse
TY for the reply.I'll try it and i ll let you know
Oh God thank you very much i think it worked.But I have another problem now.My pc doesnt recognise it.It says USB MTP failed.I know that MTP stands for Mobile Transfer Protocol but I encounter this error for the 1st time and I dont know what to do.Nevermind I ll search it myself dont bother I only have one last question.If I try once again to go back to v15.2 will I have the same problem?
P.T.J0hnnie said:
The thing with recovery mod is weird.Sometimes I can,sometimes I cannot.But when I can,it can only be a previous version of 6.0.1.2 flashed with odin and not 6.0.1.2.Right now I m trying and I cant get into recovery.I searched the official jellybean 4.1.1 for my country (greece) but cant find it and dont know what to do.:/
Click to expand...
Click to collapse
u can search it here Click
P.T.J0hnnie said:
Oh God thank you very much i think it worked.But I have another problem now.My pc doesnt recognise it.It says USB MTP failed.I know that MTP stands for Mobile Transfer Protocol but I encounter this error for the 1st time and I dont know what to do.Nevermind I ll search it myself dont bother I only have one last question.If I try once again to go back to v15.2 will I have the same problem?
Click to expand...
Click to collapse
try to redownload the file again n make sure before u flash it into ur phone check first the MD5....
jeffreydesiree said:
u can search it here Click
try to redownload the file again n make sure before u flash it into ur phone check first the MD5....
Click to expand...
Click to collapse
I didnt download the file again because I checked it immediately after I downloaded it.When I managed to boot into recovery mod(the older version)I flashed the rom again and my phone booted normally.I think that the problem-my fault-was that I flashed 15.2 over 17.1.I dont know if the problem caused by the older rom or the older kernel or the tweaks but it belongs to past right now.After that,I updated to the latest version of cwm via ROM Manager from PlayStore.
P.T.J0hnnie said:
I didnt download the file again because I checked it immediately after I downloaded it.When I managed to boot into recovery mod(the older version)I flashed the rom again and my phone booted normally.I think that the problem-my fault-was that I flashed 15.2 over 17.1.I dont know if the problem caused by the older rom or the older kernel or the tweaks but it belongs to past right now.After that,I updated to the latest version of cwm via ROM Manager from PlayStore.
Click to expand...
Click to collapse
glad to hear that...
here a little tips..
always clean everything before u flash ur phone..it might help..:good::laugh:
jeffreydesiree said:
glad to hear that...
here a little tips..
always clean everything before u flash ur phone..it might help..:good::laugh:
Click to expand...
Click to collapse
I know bro I do it always no matter what.I never forget this
Hi,
I am trying to install a rom on my n7100 for a second time. Trying to move from DN3 to SOKP (http://forum.xda-developers.com/showthread.php?t=2700230).
I'm making a clean install. However, while installing from zip I'm getting a status 7 error. I researched all around and found that it is mostly because of the assert section. So i removed it and tried; same error.
I had philz recovery installed, moved to cwm, still same error.
Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2605730 , where someone flashed original firmware and then flashed new rom; did that, same error.
Tried toggling signature verification; same error.
Now my installation screen looked like this. Can anyone help me with it? I really dont know whats happening.
anmolgoel said:
Hi,
I am trying to install a rom on my n7100 for a second time. Trying to move from DN3 to SOKP (http://forum.xda-developers.com/showthread.php?t=2700230).
I'm making a clean install. However, while installing from zip I'm getting a status 7 error. I researched all around and found that it is mostly because of the assert section. So i removed it and tried; same error.
I had philz recovery installed, moved to cwm, still same error.
Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2605730 , where someone flashed original firmware and then flashed new rom; did that, same error.
Tried toggling signature verification; same error.
Now my installation screen looked like this. Can anyone help me with it? I really dont know whats happening.
Click to expand...
Click to collapse
tried flashing another rom?
anmolgoel said:
Hi,
I am trying to install a rom on my n7100 for a second time. Trying to move from DN3 to SOKP (http://forum.xda-developers.com/showthread.php?t=2700230).
I'm making a clean install. However, while installing from zip I'm getting a status 7 error. I researched all around and found that it is mostly because of the assert section. So i removed it and tried; same error.
I had philz recovery installed, moved to cwm, still same error.
Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2605730 , where someone flashed original firmware and then flashed new rom; did that, same error.
Tried toggling signature verification; same error.
Now my installation screen looked like this. Can anyone help me with it? I really dont know whats happening.
Click to expand...
Click to collapse
Delete some apps or unwanted ringtones from the rom zip then flash the rom..
try to use newest Milestone from SOKP, where is the file saved, on sd-card or internal memory ?
Make sure the ROM zip is completely downloaded/ copies to ur SD card .. An incomplete zip is a common cause of this error, also make sure u're on the latest version of whatever recovery u're using
Sent from my GT-I9300
Thank you guys for your help. yes jinayhvora I used the newer recovery and it worked like a charm.
However latest is not always better as last time while installing DN3 I couldnt get past the terms and condition. Then I downgraded to a previous version of philz recovery and it worked.
There is another problem though, when I restore the nandroid of DN3, it works fine, but when I restore backup of stock, I cant get past the samsung logo.
I thought the backup might be corrupt, but I re-flashed the stock firmware and took its backup; same problem.
Any ideas?
It DOES say in the Installation Instructions that they recommend using TWRP. There's usually a reason why when they say that.
es0tericcha0s said:
It DOES say in the Installation Instructions that they recommend using TWRP. There's usually a reason why when they say that.
Click to expand...
Click to collapse
:good::good:
es0tericcha0s said:
It DOES say in the Installation Instructions that they recommend using TWRP. There's usually a reason why when they say that.
Click to expand...
Click to collapse
Yes I agree; can you help me with the below problem though?
anmolgoel said:
There is another problem though, when I restore the nandroid of DN3, it works fine, but when I restore backup of stock, I cant get past the samsung logo.
I thought the backup might be corrupt, but I re-flashed the stock firmware and took its backup; same problem.
Any ideas?
Click to expand...
Click to collapse
anmolgoel said:
I re-flashed the stock firmware and took its backup; same problem.
Click to expand...
Click to collapse
what do you mean by this?
You flashed the stock then restored its backup? and still got stuck? well then maybe, it really is corrupted
Are you using TWRP or CWM now? Try wiping caches after restore. But I dunno DN3 refers to either. Is that stock based or other?
kermage said:
what do you mean by this?
Click to expand...
Click to collapse
Well, what I mean by this is: I flashed the stock firmware, rooted it, and then took a nandroid backup. I wanted to see if the problem was with restoring the previous copy I have, or with restoring the stock firmware in general.
And when I restored it after a wipe, it still got stuck at the samsung logo. So the problem is with restoring the stock firmware, which is weird. I was using the latest philz recovery, and the stock firmware was 4.3
kermage said:
You flashed the stock then restored its backup? and still got stuck? well then maybe, it really is corrupted
Click to expand...
Click to collapse
maybe
anmolgoel said:
Well, what I mean by this is: I flashed the stock firmware, rooted it, and then took a nandroid backup. I wanted to see if the problem was with restoring the previous copy I have, or with restoring the stock firmware in general.
And when I restored it after a wipe, it still got stuck at the samsung logo. So the problem is with restoring the stock firmware, which is weird. I was using the latest philz recovery, and the stock firmware was 4.3
maybe
Click to expand...
Click to collapse
well, take a new backup now and try if it works..then we can conclude..
I'm curious as to why you aren't using TWRP.
kermage said:
well, take a new backup now and try if it works..then we can conclude..
Click to expand...
Click to collapse
I'm not able to make out whether you're messing with me
the current rom (SOKP) is able to be restored; only problem with the stock rom.
es0tericcha0s said:
I'm curious as to why you aren't using TWRP.
Click to expand...
Click to collapse
because the backup was made in philz. From what I know, CWM and TWRP have different kind of backup files which cant be restored by the other.. let me know if I'm wrong..
Should I use TWRP to backup now.. You think it'll work better than philz?
es0tericcha0s said:
Are you using TWRP or CWM now? Try wiping caches after restore. But I dunno DN3 refers to either. Is that stock based or other?
Click to expand...
Click to collapse
sorry didnt see this post earlier.. I'm on philz, DN3 is ditto note 3 rom that I was using; it is stock based.
The backups are not compatible between the 2, but obviously this version of Philz isn't cooperating like it should and since the developer's for DU suggested TWRP, seems like that's next logical step in troubleshooting issues with backing up and restoring in general.
es0tericcha0s said:
The backups are not compatible between the 2, but obviously this version of Philz isn't cooperating like it should and since the developer's for DU suggested TWRP, seems like that's next logical step in troubleshooting issues with backing up and restoring in general.
Click to expand...
Click to collapse
Agreed.. Just to put it out there.. the first backup I made was through Online nandroid manager app, and the second one through philz..
I'll install and use twrp the next time I'm on stock... which I dont think i will be for a long time btw.. enjoying the irresistible ROMs out there
anmolgoel said:
Agreed.. Just to put it out there.. the first backup I made was through Online nandroid manager app, and the second one through philz..
I'll install and use twrp the next time I'm on stock... which I dont think i will be for a long time btw.. enjoying the irresistible ROMs out there
Click to expand...
Click to collapse
Ah. Never used the Online Nandroid one. Never saw the point and trust the actual recovery to be able to backup better. Less chance of issues.
Today, I tried to flash Project Infinity on my 900T and after doing so, I am stuck in a boot loop. I tried to format /system and re installing but that led to no success. Any help?
may be bad download? did u checksum? try redownload and select stock kernel see how it goes.
koolboyztn said:
may be bad download? did u checksum? try redownload and select stock kernel see how it goes.
Click to expand...
Click to collapse
Well I eventually got it to work but when I booted it, things were really buggy and I really couldn't do anything. When I would go through the initial setup of the Project Infinity ROM, there would be a constant error message like: "com.systemui has stopped" and everything was unresponsive. So I flashed the stock ROM and i'm back to vanilla touchwiz.
Also, what is checksum?
flibble3 said:
Well I eventually got it to work but when I booted it, things were really buggy and I really couldn't do anything. When I would go through the initial setup of the Project Infinity ROM, there would be a constant error message like: "com.systemui has stopped" and everything was unresponsive. So I flashed the stock ROM and i'm back to vanilla touchwiz.
Also, what is checksum?
Click to expand...
Click to collapse
Did you wipe data / cache before flashing?
Exel said:
Did you wipe data / cache before flashing?
Click to expand...
Click to collapse
Yea, I did.
checksum is just the way to check made sure u got a good download.
koolboyztn said:
checksum is just the way to check made sure u got a good download.
Click to expand...
Click to collapse
How do I do that?
diiferent files manager app have different way to check, u may need to google it.
koolboyztn said:
diiferent files manager app have different way to check, u may need to google it.
Click to expand...
Click to collapse
I found a way, but the developer doesn't provide a md5 checksum so i'm lost there. Do you think using a different recovery will help?