Hi guys,
Before registering ID in this forum, I have already tried all methods but still failed.
the story is:
1. I was using unloot stock rom for near one year. I installed too many software, it became slow and losing power so quickly.
2. Then I looted it, still use stock rom, I found root was not perfect, sometimes lost control, will reboot automatically.
3. I decided to fully loot it. Then I use custom recovery and "nameless rom", its a good rom, but the phone sometimes show boot loop. I think that's OK at least boot loop is not frequent.
4. last week, I flashed another custom rom ”CM12.1“ ,much smoother, howerver, disaster began, just using less then half day, it is always on boot loop!!!!
now I even can't use my phone, already tried two WIPE in recovery, take out battery.....
flash original stock with Odin, show green PASS, but still on boot loop.
the worst situation now is it boots too fast to get in recovery!!!
please help
You just can't keep flashing any roms as u wish. I hope u know the concept of bootloaders and baseband versions... lets say for example ur flashing a rom having baseband version say "ABC", so even though u have a custom recovery and wipe data and all that, u cannot install another rom having baseband version say "XYZ". For that u have to flash the bootloader made for that baseband version from odin first. Got it?
Shane_Picardo said:
You just can't keep flashing any roms as u wish. I hope u know the concept of bootloaders and baseband versions... lets say for example ur flashing a rom having baseband version say "ABC", so even though u have a custom recovery and wipe data and all that, u cannot install another rom having baseband version say "XYZ". For that u have to flash the bootloader made for that baseband version from odin first. Got it?
Click to expand...
Click to collapse
I tried, still bootloop
kyle1031 said:
I tried, still bootloop
Click to expand...
Click to collapse
Now (assuming u have done a clean install of the stock rom with same bootloader & modem and still getting boot loop) go to recovery and wipe data factory reset. And wipe cache. And reboot. It MUST work fine now!
Shane_Picardo said:
Now (assuming u have done a clean install of the stock rom with same bootloader & modem and still getting boot loop) go to recovery and wipe data factory reset. And wipe cache. And reboot. It MUST work fine now!
Click to expand...
Click to collapse
I tried, still bootloop
This method worked fine with me and everyone. It should work with u too. Now in ur case even after doing a clean install of the stock rom with bootloader & modem, and ur still getting a boot loop... then I suggest u take it to the service center. If u have tripped ur knox but u installed clean stock rom, service center will charge u about 150 Rs. (3 dollars) to fix the issues.
Shane_Picardo said:
This method worked fine with me and everyone. It should work with u too. Now in ur case even after doing a clean install of the stock rom with bootloader & modem, and ur still getting a boot loop... then I suggest u take it to the service center. If u have tripped ur knox but u installed clean stock rom, service center will charge u about 150 Rs. (3 dollars) to fix the issues.
Click to expand...
Click to collapse
Thanks buddy
Related
So i tried to flash a rom like a normally do and i get stuck on the green screen.
I noticed now when flashing a rom is takes alot longer to flash then it usually did , i wiped pulled battery multiple times and still the same results. If i try to flash a froyo rom it will stay on the mytouch screen for a few secs and reboot to recovery mode on its own. every other rom just gets stuck and will not move. im limited to only recovery mode and Fastboot , are their any simple fixes that can be done and thanks in advance.
fabolous02000 said:
So i tried to flash a rom like a normally do and i get stuck on the green screen.
I noticed now when flashing a rom is takes alot longer to flash then it usually did , i wiped pulled battery multiple times and still the same results. If i try to flash a froyo rom it will stay on the mytouch screen for a few secs and reboot to recovery mode on its own. every other rom just gets stuck and will not move. im limited to only recovery mode and Fastboot , are their any simple fixes that can be done and thanks in advance.
Click to expand...
Click to collapse
Have you tried fixing apk uids? I've also heard you can use the bootloader to do a more thorough wipe.
If I were in your situation I would apply sappimg to unroot and start over.
Phateless said:
Have you tried fixing apk uids? I've also heard you can use the bootloader to do a more thorough wipe.
If I were in your situation I would apply sappimg to unroot and start over.
Click to expand...
Click to collapse
im fairly new so i only know how to flash roms . outside of that im pretty much clueless. I tried flashing a new radio & when it tells me to reboot to complete installation it says no more room or somthing like that. it does it really quick so i cant tell. Also how would i go about unrooting?
EDIT .. ok unrooted the phone and it seemed to have done the trick.
fabolous02000 said:
im fairly new so i only know how to flash roms . outside of that im pretty much clueless. I tried flashing a new radio & when it tells me to reboot to complete installation it says no more room or somthing like that. it does it really quick so i cant tell. Also how would i go about unrooting?
EDIT .. ok unrooted the phone and it seemed to have done the trick.
Click to expand...
Click to collapse
Glad you're still operational. Now you can retrace your steps and figure out where you went wrong. I also had to unroot and go back to Cupcake before I successfully completed my first rooting.
If you're just flashing ROMs, I would stay away from updating the radio unless the developer specifically says you should.
I Think i have bricked my nexus s ......it wont startup and goes to do first setup but force closes....i can access recovery but when i flash a rom it aborts ....only just bought it
U can odin it back to stock. Check out the android dev forums
Sent from my Nexus S using XDA App
afishpie said:
U can odin it back to stock. Check out the android dev forums
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Please can you elaborate...or point me in right direction......recovery is now only accessible by flashing it first....phone just wont do anything
download a 2.3.3 nandroid backup and restore to it using clockwork recovery
ignore odin.
http://forum.xda-developers.com/showthread.php?t=884093
update to 2.3.3 using http://android.clients.google.com/p...2cf141e6a.signed-soju-ota-102588.f182cf14.zip
or just download CM7 and flash that along with gapps (wipe dalvik/cache/factory)
and your phone is not bricked. the definition of a bricked phone is a phone who cannot access recovery/fastboot/etc.. can access absolutely nothing
Well, he does say that his attempts to flash a rom always abort...
OP, we need more details.
Are you using Clockwork Recovery? Which version? Try an older/newer version...
What ROM are you trying to flash? Have you tried others?
What happens when you try a normal boot? You say you get as far as the first setup screen?
Have you tried a Factory Reset of the phone from within recovery (stock or clockwork)?
distortedloop said:
Well, he does say that his attempts to flash a rom always abort...
OP, we need more details.
Are you using Clockwork Recovery? Which version? Try an older/newer version...
What ROM are you trying to flash? Have you tried others?
What happens when you try a normal boot? You say you get as far as the first setup screen?
Have you tried a Factory Reset of the phone from within recovery (stock or clockwork)?
Click to expand...
Click to collapse
Many thanks to both of you.....for your help .....so much appreciated......i have got past first setup screen after applying a nandroid backup......it finally worked after 5 times trying....but i have stock android recovery but rom manager on phone .....how can i get clockwork mod back as everytime i flash it.....i get to use it for that one instance ans then it returns to stock android recovery
I think it might be okay now ....after titanium said busybox was installed....i dont think it was done correectly.....after downloading busy box from market....recovery seems to be sticking rather then reverting back to android. Just to check....is there anything i should do to check all is well on my phone and also while flashing i think i changed build number from IR to GH (what are the implications of this move? many thanks...phew
EDIT- NO recovery still wont stay....any ideas?
menov321 said:
I think it might be okay now ....after titanium said busybox was installed....i dont think it was done correectly.....after downloading busy box from market....recovery seems to be sticking rather then reverting back to android. Just to check....is there anything i should do to check all is well on my phone and also while flashing i think i changed build number from IR to GH (what are the implications of this move? many thanks...phew
EDIT- NO recovery still wont stay....any ideas?
Click to expand...
Click to collapse
That's normal. See below:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else
sano614 said:
That's normal. See below:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else
Click to expand...
Click to collapse
Thankyou SOOO MUCH.....you put my mind at rest......can you maybe help me with one other thing.....WHEN I MESSED UP EARLIER i flashed a different rom build.....does this have any negative affect on the phone....my stock rom was a IR something but i flashed a GR or GH something....
menov321 said:
Thankyou SOOO MUCH.....you put my mind at rest......can you maybe help me with one other thing.....WHEN I MESSED UP EARLIER i flashed a different rom build.....does this have any negative affect on the phone....my stock rom was a IR something but i flashed a GR or GH something....
Click to expand...
Click to collapse
No it doesn't. You're fine. The latest is android 2.3.3 with GRI40.
Sent from my Nexus S using Tapatalk
Hi,
I flashed the google edition rom a few weeks ago, all was working fine. This morning, I decided to flash a stock rom from sammobile (was this a bad idea)? I used CF autoroot and twerp custom recovery. It failed. So wiped everything, reflashed the google edition rom, but when I reboot the phone it gets stuck showing "Samsung galaxy s4" white text.
To boot it again i have to wipe data, cache and dalvik, then reflash the ROM, then qipe cache and dalvik, then it reboots. But when I turn it off then on again the whole process starts again.
Can anybody tell me what I'm doing wrong? This is the same ROM that worked faultlessly for weeks...
Thanks
Did u wait long enough, first reboot after flashing a new rom can take a while.
Sent from my GT-I9505 using XDA Premium HD app
richard2311 said:
Did u wait long enough, first reboot after flashing a new rom can take a while.
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
Yeah, I gave it 5 minutes, but it's not even getting to the boot animation.
When I tried to flash the stock rom could that have messed something up? It said failed, then for ages after that, it kept saying "error-failed to open \data\data .... I/O error" in twrp.
To avoid that I have to wipe data seperately, reboot recovery, then flash the ROM again from scratch. Every time I reboot the phone I have to do a full wipe and flash the rom before it even boots..
dickson123 said:
Yeah, I gave it 5 minutes, but it's not even getting to the boot animation.
When I tried to flash the stock rom could that have messed something up? It said failed, then for ages after that, it kept saying "error-failed to open \data\data .... I/O error" in twrp.
To avoid that I have to wipe data seperately, reboot recovery, then flash the ROM again from scratch. Every time I reboot the phone I have to do a full wipe and flash the rom before it even boots..
Click to expand...
Click to collapse
Have a read if this great guide: http://forum.xda-developers.com/showpost.php?p=43340522&postcount=3297
mobileguynz said:
Have a read if this great guide: http://forum.xda-developers.com/showpost.php?p=43340522&postcount=3297
Click to expand...
Click to collapse
Ok, thanks, I'll give it a go later. I'm at work and was hoping for a solution that didn't require ODIN (work PC too locked-down )
dickson123 said:
Ok, thanks, I'll give it a go later. I'm at work and was hoping for a solution that didn't require ODIN (work PC too locked-down )
Click to expand...
Click to collapse
Well depending on which stock ROM you flashed you maybe affected by the enabled SElinux issue see https://plus.google.com/app/basic/stream/z13xxnmzvyeihn00w23wcdp55terwvove
mobileguynz said:
Well depending on which stock ROM you flashed you maybe affected by the enabled SElinux issue see https://plus.google.com/app/basic/stream/z13xxnmzvyeihn00w23wcdp55terwvove
Click to expand...
Click to collapse
I don't understand what the issue is though. I'm not doing anything different than I did 3 weeks ago, and yet this time it doesn't work.
It's now gotten to the stage where it won't boot at all, just sits at the white text, no boot animation.
Is it possible that flashing a stock un-rooted ROM has messed it up somehow? Technically it never flashed because it just failed immediately.
dickson123 said:
I don't understand what the issue is though. I'm not doing anything different than I did 3 weeks ago, and yet this time it doesn't work.
It's now gotten to the stage where it won't boot at all, just sits at the white text, no boot animation.
Is it possible that flashing a stock un-rooted ROM has messed it up somehow? Technically it never flashed because it just failed immediately.
Click to expand...
Click to collapse
If you flashed the latest stock ROM it maybe be one with Knox and that has a secure boot loader and kernel secure Selinux Knox stops you from modifying and installing.
Try using ausdims v16 kernel or wadams Adam kernel for stock roms. Note when I flashed the last ROM waited 10 minutes and had do a wipe and reset for it to boot see last pages for discussion http://forum.xda-developers.com/showthread.php?t=2250824
http://forum.xda-developers.com/showthread.php?t=2250824
Hey wassup. So yesterday I rooted my phone and tried to install CM13 on it. Took a few tries since the rom I got was corrupted but I got it to work. Then I noticed it was guzzling the battery like lemonade (this EXACT same thing happened on my previous S4 too) so I gave up on it and decided to revert back to the stock rom. Everything went well... NOT. I downloaded the stock firmware (3gigs... zzz) and I flashed it with Odin and the phone restarted. The little android robot from the default unrooted recovery popped up and it had below it this: "Installing system update..." and then out of the blue it said "Erasing" and it's gear started rotating backwards. THEN, when it finished the normal Samsung Galaxy Note 4 logo popped up, went away and then CAME BACK AGAIN FOR LIKE 500 TIMES AND COUNTING. AOSP roms work just fine, it's just that touchwiz ones won't work whatsoever (even tried sixperience, no luck)... What should I do? I already lost my S4 due to this...
install TWRP custom recovery, boot up in recovery format system dalvik cache and internal storage then try flashing stock with odin hopefully it will work.
Try to remove battery first.from tsoch recovery wipe data cache and see if it works
dork997 said:
install TWRP custom recovery, boot up in recovery format system dalvik cache and internal storage then try flashing stock with odin hopefully it will work.
Click to expand...
Click to collapse
Been there, done that. Nope, still refuses to work :/
bumpity bump bump
Did you backup your efs partition before you flashed cm13? If not you corrupted your efs and your phone is a wifi tablet now because you cant use your modem.
travis82 said:
Did you backup your efs partition before you flashed cm13? If not you corrupted your efs and your phone is a wifi tablet now because you cant use your modem.
Click to expand...
Click to collapse
this never happened to me with my old s2 or s4
why is it happening now ?
Didn't backup. Now it just won't even work with odin. Whenever I try to just flash anything with it goes off and says 0 successes and 0 fails. What I did notice though was that whenever I installed a stock rom it starts this "Installing system update" with the android robot twingling it's antennaes and then out of nowhere it's blue bar goes away and it says "Erasing" then... bootloop. Now odin won't even work (explained above). Should I just give up and send it in for repairing? Or can ANYONE send me the twrp restore file, please...
Peontikos_Desmos said:
Didn't backup. Now it just won't even work with odin. Whenever I try to just flash anything with it goes off and says 0 successes and 0 fails. What I did notice though was that whenever I installed a stock rom it starts this "Installing system update" with the android robot twingling it's antennaes and then out of nowhere it's blue bar goes away and it says "Erasing" then... bootloop. Now odin won't even work (explained above). Should I just give up and send it in for repairing? Or can ANYONE send me the twrp restore file, please...
Click to expand...
Click to collapse
Hi
Same problem
Any ideas !!!
Hey,
I have the same problem it turns out after flashing, i cant remember, maybe dytto note 4 rom, it got stuck in continous bootloops and the only way it is working for me is when its charging. I know it sounds crazy but its the only way for me, ive tried installing stock different countries firmware and bunch of custom rom with no luck. I sent it to the place where i bought the phone and made myself look dumb asking why it is like that and i told them i had not do anything. After only a week they phoned me and said it was rooted (i did get the root out when i gave it but they somehow knew it was... later i understood that it is all about that stupid Know thing) and refused to cover my warranty. They said that the only way i can get it to work is to pay 300$ for new chip :,(
senon said:
Hey,
I have the same problem it turns out after flashing, i cant remember, maybe dytto note 4 rom, it got stuck in continous bootloops and the only way it is working for me is when its charging. I know it sounds crazy but its the only way for me, ive tried installing stock different countries firmware and bunch of custom rom with no luck. I sent it to the place where i bought the phone and made myself look dumb asking why it is like that and i told them i had not do anything. After only a week they phoned me and said it was rooted (i did get the root out when i gave it but they somehow knew it was... later i understood that it is all about that stupid Know thing) and refused to cover my warranty. They said that the only way i can get it to work is to pay 300$ for new chip :,(
Click to expand...
Click to collapse
ffs i'm not paying another phone's worth in a ****ing motherboard. I tried:
-Flashing the stock bootloader, fails at sboot.img:NAND Write start fail
-Flashing the PIT file, just... wont flash. Successes 0/Fails 0
-Flashing the stock AP file, bootloop
-Flashing the CP and the CSC stock files, serial(com) port cannot be opened.
****ing garbage. For some reason my phone's the only exception to the rule that phones able to boot into download mode are salvageable. It's going in for a repair and if it's more than $50 I'm not rooting again even at gunpoint.
Quick update:
I found a toolkit that has a flash stock boot image option. Had to recover to my cm13 backup to enable usb debugging. Will post results
Nothing of course...
try this step by step,
1. Download stock firmware THE LATEST ONE (n910c v5.1.1) from sammobile.com
2. Download newest Odin and Samsung USB; installed Samsung USB
3. I am assuming you have installed twrp recovery. Boot to twrp recovery and do a full wipe; wipe all!
4. Boot to downloading mode and install stock via odin. That is it.
Ps.... in case of failure, make sure you have installed Samsung USB! Or just reconnect usb cable with other usb ports untill it is working.
Never flach cm if doesn'T HAVE a efs backup if not you will stuck with cm
Oliva.raiders said:
1. Download stock firmware THE LATEST ONE (n910c v5.1.1) from sammobile.com
2. Download newest Odin and Samsung USB; installed Samsung USB
3. I am assuming you have installed twrp recovery. Boot to twrp recovery and do a full wipe; wipe all!
4. Boot to downloading mode and install stock via odin. That is it.
Ps.... in case of failure, make sure you have installed Samsung USB! Or just reconnect usb cable with other usb ports untill it is working.
Click to expand...
Click to collapse
Well, crap I already sent it in for repairing but if the fuqing robbers decide to change the motherboard instead of doing anything to it and charge me 500$ to do so I'm getting it back and I'm trying this one. Already did but it wouldn't hurt retrying... BTW FOR THE LOVE OF GOD DOES SOMEONE HAVE A TWRP BACKUP FILE ON STOCK TOUCHWIZ? JESUS
radium56ad said:
Never flach cm if doesn'T HAVE a efs backup if not you will stuck with cm
Click to expand...
Click to collapse
Is there absolutely NO workaround?
i had the same issue, this is how i solved this (you won't like it):
-deleted efs partition
-restored 5.1.1 coj5 via odin
-then took it to a samsung repair center to restore the imei
paid them like 50 bucks...that sucks. after this im backing up efs folder before flashing a rom.
radium56ad said:
Never flach cm if doesn'T HAVE a efs backup if not you will stuck with cm
Click to expand...
Click to collapse
JuanWilliman said:
i had the same issue, this is how i solved this (you won't like it):
-deleted efs partition
-restored 5.1.1 coj5 via odin
-then took it to a samsung repair center to restore the imei
paid them like 50 bucks...that sucks. after this im backing up efs folder before flashing a rom.
Click to expand...
Click to collapse
Oh that's nothing man. The fuqing scammers told me the whole freaking board had to be replaced...
There's one thing I've noticed though that's PROBABLY gotta be the culprit. Whenever I install a touchwiz rom, the phone boots up fine for once, shows the robot with the "Installing system update" and then it goes off with "Erasing" followed by the bootloop. Could anyone please elaborate on this? I have a feeling this is what's causing this ****fest
I was rooting my device and was successful l in that. I flashed TWRP and Magisk and after that I decided to install a custom ROM. While going for it I again wiped the - Delvik Cache, System, Data and Cache. And when I tried installing that ROM it doesn't gets install. Moreover I can't boot into System anymore and now I'm stucked at the screen saying "Your device has been unlocked and can't be trusted." Also the screen is showing "ID:N/A"
So please please please help me with this problem ASAP. I can't use my phone now please and I regret for what I've done.
Try booting into fastboot mode. Hold down volume down and power for several seconds. If you can get there, you can flash the stock ROM and hopefully get back to normal. There are other threads that show you how to install. Make sure you use a version that is greater than or equal to what you last had installed.
NZedPred said:
Try booting into fastboot mode. Hold down volume down and power for several seconds. If you can get there, you can flash the stock ROM and hopefully get back to normal. There are other threads that show you how to install. Make sure you use a version that is greater than or equal to what you last had installed.
Click to expand...
Click to collapse
So this means my Stock ROM is gone? and I've to install it again? Can u explain me what my problem is?
engtika said:
So this means my Stock ROM is gone? and I've to install it again? Can u explain me what my problem is?
Click to expand...
Click to collapse
When you installed a custom ROM your stock ROM was gone. That's how it works. But the reason you're stuck at the screen you're at, I don't know.
Restoring back to stock is the first thing I'd try to see if you can actually use your phone
NZedPred said:
When you installed a custom ROM your stock ROM was gone. That's how it works. But the reason you're stuck at the screen you're at, I don't know.
Restoring back to stock is the first thing I'd try to see if you can actually use your phone
Click to expand...
Click to collapse
Thanks for the information you provided regarding my problem. Now I've installed the Stock ROM and my dead phone is back to life. ?