I was updating my mdl s4 to a new build and flashed a rom for t0ltetmo, a T-Mobile note, by accident. I believe it updated the bootloader but not totally sure.
This is the error I get from TWRP when trying to flash a backup:
twrp E: unable ti mount ' /system'
If I go back to stock using kies can I then root with casual? Or will kies change my bootloader to something undesirable (mk1, nb1, etc.)
Any help would be greatly appreciated.
Have you tried flashing the correct firmware in Odin? You may have bricked your device, but it's a good sign you can still get into twrp.
Sent from my Nexus 5
No haven't tried Odin. I only have a Mac, need to borrow a friends PC. Don't think it's bricked. I believe it has the note 2 bootloader, and that's why TWRP isn't flashing the backup
numbere said:
No haven't tried Odin. I only have a Mac, need to borrow a friends PC. Don't think it's bricked. I believe it has the note 2 bootloader, and that's why TWRP isn't flashing the backup
Click to expand...
Click to collapse
If odin doesnt work, check out mobiletechvideos.com they fixed my bricked S4.
numbere said:
No haven't tried Odin. I only have a Mac, need to borrow a friends PC. Don't think it's bricked. I believe it has the note 2 bootloader, and that's why TWRP isn't flashing the backup
Click to expand...
Click to collapse
You could try a Windows vm on the Mac
Sent from my Nexus 5
Will try running odin on windows vm. Do you know if I go back to stock using kies if the bootloader will update to something other than the original MDL?
numbere said:
Will try running odin on windows vm. Do you know if I go back to stock using kies if the bootloader will update to something other than the original MDL?
Click to expand...
Click to collapse
If you use kies it'll force the latest firmware. You want to use Odin.
Sent from my Nexus 5
jd1639 said:
If you use kies it'll force the latest firmware. You want to use Odin.
Sent from my Nexus 5
Click to expand...
Click to collapse
Thanks for all the support! That was a scary situation.
Got Odin to run on parallels. Before using Odin I gave twrp one last try. Factory reset and then flashed a rom I tried previously, but this time without the gapps. Success! Got very lucky on this mistake.
Word to the wise double check your rom before flashing.
numbere said:
Thanks for all the support! That was a scary situation.
Got Odin to run on parallels. Before using Odin I gave twrp one last try. Factory reset and then flashed a rom I tried previously, but this time without the gapps. Success! Got very lucky on this mistake.
Word to the wise double check your rom before flashing.
Click to expand...
Click to collapse
Glad you got it working. It may have been a bad download of gapps.
Sent from my Nexus 5
No I definitely flashed a rom for the note 2.
Makes me think it's a sign that the software in our community is becoming more stable. Meaning that one can flash the incorrect ROM and potentially not destroy their device.
Sent from my SGH-I337 using XDA Premium 4 mobile app
numbere said:
No I definitely flashed a rom for the note 2.
Makes me think it's a sign that the software in our community is becoming more stable. Meaning that one can flash the incorrect ROM and potentially not destroy their device.
Sent from my SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No, you got lucky. The partitions are different for different devices and that's what will get you. I.e.flash a boot img where system is supposed to be and you'll be hard bricked
Sent from my Nexus 5
Wow, what a coincidence.
I had a similar issue over the last couple of days.
Here: http://forum.xda-developers.com/showthread.php?t=2701379
I used Odin in VMWare Fusion and it would not work at all, except to flash bootloaders and kernels. I finally got it to work through using heimdall using this thread: http://forum.xda-developers.com/showthread.php?t=2374441
Related
I can't seem to find a thread to help me restoring my nexus s back to a factory state.
I did flash via adb, but I am having issues with my phone, so I want to re flash.
Thanks for your help
Matt
Code:
fastboot oem lock
fastboot oem unlock
(then lock again if you want)
That will erase EVERYTHING. Then you can flash clockwork back. Then flash one of the stock ROMs (found here on the forums somewhere or from ROM Manager). Basically back to stock. (With custom bootloader). Which you can also get rid of, I just don't remember how
Why not just flash the newest stock from samfirmwares via Odin? Semms quicker and easier to me, but ... are there any disadvantages?
fallenguru said:
Why not just flash the newest stock from samfirmwares via Odin? Semms quicker and easier to me, but ... are there any disadvantages?
Click to expand...
Click to collapse
I've always considered Odin to be a last resort kind of thing. You really shouldn't Odin unless everything else doesn't work and your phone is near screwed. The reason being, should anything go wrong during the Odin flashing, your device runs a very high risk of permanently bricking and the past the point of no return. Its probably the only way of permanently bricking your Nexus.
Sent from my Nexus S using XDA App
Hmm, ok.
I've always used Odin for my Samsung i5700 (Galaxy Spica), mainly because there is nothing else for it. It's always seemed extremely stable and lightweight to me, never mind the factory floor look.
AFAICT Odin can only brick your phone if your computer explodes at exactly the right time (i. e. while it's flashing the bootloader) - no idea if fastboot has additional safeguards or something.
An inexperienced user has a much better chance of screwing up in a multi-step restore, so if the objective is to restore to an out-of-the-box state then I'd still rather use Odin, personally. (For modding parts of firmware and comfort, fastboot beats it hands down.)
I came from the Vibrant, so I see where you're coming from. But like you said, an inexperienced user has a better chance of screwing it up. That's why I recommended the non-odin method to the OP. To each his own I guess. Both methods will take you to the same end result, one which is slightly less of a hassle. I just cringe everytime I use Odin in fear of windows crashing or Odin crashing since previous versions were known to be relatively unstable. Or some other mishap like kicking the USB cable while flashing.
Sent from my Nexus S using XDA App
I just used odin and ROM from here
http://forum.xda-developers.com/showthread.php?t=947950
Restore 2.3.1 through CWM
http://forum.xda-developers.com/showthread.php?t=884093
download the nandroid backup in that thread and restore using cwm. then do a factory reset and lock bootloader with "fastboot oem lock". that's what i did.
peeturr said:
I came from the Vibrant, so I see where you're coming from. But like you said, an inexperienced user has a better chance of screwing it up. That's why I recommended the non-odin method to the OP. To each his own I guess. Both methods will take you to the same end result, one which is slightly less of a hassle. I just cringe everytime I use Odin in fear of windows crashing or Odin crashing since previous versions were known to be relatively unstable. Or some other mishap like kicking the USB cable while flashing.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
while i can agree that odin is not very... user friendly in the sense of many errors. it is very slim chance of it causing a brick. and why not just use heimdall? its the open source solution to odin
Check the Q&A section. Yet another nexus S perma-bricked using Odin. In this case he used the wrong files (i9023 instead of i9020) to flash. Anything could happen. If you could avoid it, you really should because Odin messes with very sensitive files.
Sent from my Nexus S using XDA App
peeturr said:
I've always considered Odin to be a last resort kind of thing. You really shouldn't Odin unless everything else doesn't work and your phone is near screwed. The reason being, should anything go wrong during the Odin flashing, your device runs a very high risk of permanently bricking and the past the point of no return. Its probably the only way of permanently bricking your Nexus.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
What permabrick using odin, never happen.
Sent from my SPH-D700 using XDA App
U can't permbrick your phone with odin
Sent from my Nexus S using XDA App
demo23019 said:
U can't permbrick your phone with odin
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Try loading i9023 Odin files onto your i9020.
Sent from my Nexus S using XDA App
peeturr said:
Try loading i9023 Odin files onto your i9020.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
dont do that that'll mess up with the phone's functionality because it'll start acting like a 9023 when its a 9020.
Maybe the procedure here may help you.
http://theunlockr.com/2011/01/20/how-to-unroot-the-nexus-s/
Actually, I'm quite sure you can brick phones with Odin, if you try. Flashing the wrong firmware (or any other random bucket of bits) certainly works, as you can see. But I'm curious, how would fastboot have prevented this?
Sorry to the OP, I neither wanted to derail your thread nor start a holy war, just offer another option.
well it goes without saying to not use another phones firmware... but using the correct firmware on the correct phone odin has a small chance at bricking.. and thats only when your flashing boot.img and sbl.bin. he shouldnt be using the pit as odin pulls it from the phone. and there is almost no reason to repartition the device.
nabiladeeb said:
Maybe the procedure here may help you.
Click to expand...
Click to collapse
Thanks, really helpfull!
I have a problem;Do I have a I9020 or I9023?
When I look in settings-about phone it is Baseband version I9023XXKB1, but if I look in the fastboot mode I find Baseband version I9020XXKB1.
Witch one is correct?
Please help,
Thank you
peeturr said:
Try loading i9023 Odin files onto your i9020.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
shame on someone using a rom not even made for there phone but still i dont see how that will perm brick your phone when you can still access download mode
So I've had this problem for a while and I think at one point I knew what the issue was, but things came up and I guess I lost my place. I have a GS4 running 4.3 on AT&T, but if I recall correctly it took a long time (longer than it was supposed to in US) for even that update to become available to me. I'm not sure if this phone is set as a different country or something, but I seem to think that had something to do with it when I checked last time. Now when I check for updates, it does say I have an available update (KitKat?) but fails when attempting to update. Download is successful, but install is not. Baseband is I337ucuemk2 if that helps anything. Any help here would be appreciated, thanks.
Install is failing as some of the files it is trying to update has been modified. You would have to be on stock for the update to work.
Remember that there is no direct root method for KitKat yet.
http://forum.xda-developers.com/showthread.php?t=2616221 for more info
Sent from my GT-I9505 using Tapatalk
jmjoyas said:
Install is failing as some of the files it is trying to update has been modified. You would have to be on stock for the update to work.
Remember that there is no direct root method for KitKat yet.
http://forum.xda-developers.com/showthread.php?t=2616221 for more info
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
I'm actually not rooted, already stock and still having errors still...any idea why that would be?
Anyone have any advice?
Anyone have any advice?
Click to expand...
Click to collapse
Have you changed any system files and do you have xposed running? They'll break the ota.
Edit, I should have read closer. I think there is an update.zip file you could flash in the general forum. I'll look and see if I can find it.
See post 2 http://forum.xda-developers.com/showthread.php?p=50667360
Sent from my Nexus 5
jd1639 said:
Have you changed any system files and do you have xposed running? They'll break the ota.
Edit, I should have read closer. I think there is an update.zip file you could flash in the general forum. I'll look and see if I can find it.
See post 2 http://forum.xda-developers.com/showthread.php?p=50667360
Sent from my Nexus 5
Click to expand...
Click to collapse
Thanks for the link, so I should just flash the md5 with Odin? Appreciate the help.
Imnice777 said:
Thanks for the link, so I should just flash the md5 with Odin? Appreciate the help.
Click to expand...
Click to collapse
No, flash the update.zip in the stock recovery
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
No, flash the update.zip in the stock recovery
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Ok cool, thanks again...however now another issue. I've tried several times, I can not boot into recovery. Any time I try to the phone just goes black until I let go and then reboots. Even if I get the blue print in the top left, the phone does not boot into recovery. Any idea why this would be?
Imnice777 said:
Ok cool, thanks again...however now another issue. I've tried several times, I can not boot into recovery. Any time I try to the phone just goes black until I let go and then reboots. Even if I get the blue print in the top left, the phone does not boot into recovery. Any idea why this would be?
Click to expand...
Click to collapse
If you can get into download mode you may be better off flashing the md5 and Odin. Don't know why you can't get into recovery
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
If you can get into download mode you may be better off flashing the md5 and Odin. Don't know why you can't get into recovery
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Me either, guess I'd just flash normally like I would a rom? Or would an update be different. I haven't done this in a while.
Imnice777 said:
Me either, guess I'd just flash normally like I would a rom? Or would an update be different. I haven't done this in a while.
Click to expand...
Click to collapse
If you flash the tar in Odin it's going to wipe your device so backup what you can. You'll need to download the tar file to your pc and download Odin to it too if you don't already have it. You run Odin from the pc
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
If you flash the tar in Odin it's going to wipe your device so backup what you can. You'll need to download the tar file to your pc and download Odin to it too if you don't already have it. You run Odin from the pc
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Ok so I finally got into recovery, but am I supposed to rename the file or anything? It keeps telling me:
"-- Verify the file type of MD5, Before Install /sdcard ...
-- Install /sdcard"
Imnice777 said:
Ok so I finally got into recovery, but am I supposed to rename the file or anything? It keeps telling me:
"-- Verify the file type of MD5, Before Install /sdcard ...
-- Install /sdcard"
Click to expand...
Click to collapse
Anyone ever see that error before?
Imnice777 said:
Anyone ever see that error before?
Click to expand...
Click to collapse
Are you trying to flash the update.zip? I'd re-download it. It could be a bad download
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Are you trying to flash the update.zip? I'd re-download it. It could be a bad download
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
So... pretty unhappy. Downloaded the update.zip and flashed in stock recovery, it wiped my whole phone and still didn't update. I saw a couple error messages appear as it was "updating" so now I'm still on old firmware and lost everything on my phone. Luckily I did a Kies backup but still pretty ridiculous. I still lose all save data from apps and all convenience that there was from using my phone for as long as I did. Just wanted to update, shouldn't be this big of a mess. Not sure what to do next.
Imnice777 said:
So... pretty unhappy. Downloaded the update.zip and flashed in stock recovery, it wiped my whole phone and still didn't update. I saw a couple error messages appear as it was "updating" so now I'm still on old firmware and lost everything on my phone. Luckily I did a Kies backup but still pretty ridiculous. I still lose all save data from apps and all convenience that there was from using my phone for as long as I did. Just wanted to update, shouldn't be this big of a mess. Not sure what to do next.
Click to expand...
Click to collapse
Well that sucks. No idea how it works wipe you're device. It shouldn't touch the userdata. If it's truly wiped I'd Odin the nb1 tar at this point. Get it updated and start over
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Well that sucks. No idea how it works wipe you're device. It shouldn't touch the userdata. If it's truly wiped I'd Odin the nb1 tar at this point. Get it updated and start over
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
That's what I did and I'm finally updated, but pretty disappointed that it took all that just for an update. Hopefully things like that don't continue in future updates...
I need Major help with my phone. So here's the run down.
Starting on a Tuesday my phone started acting funny, it would get to the AT&T logo and stop, but then if I removed the battery and hold down the power button for roughly 20 seconds and start it up it would come on without any problems that I could see. Through the week it got worse, and by that I mean that it would restart on it's own, randomly. By that Sunday pulling the battery and holding the power button no longer did anything and from what I understand it is stuck in a boot loop.
I should have started by asking all of you, but unfortunately for me I tried fixing it myself by searching for the answers.
This is where my phone sits. It was rooted, but there is no back up. I can get to the Android system recovery. I foolishly did a reset and cleared my phone (I have all of my info and pics backed up so I'm not worried about that). My computer does not recognize my phone unless I go into the ADB setting in recovery mode and as far as I can tell the computer just knows that something is connected through USB but can't quite tell what it is. Kies has been installed on said computer recently so I have the newest Samsung drivers. I have a 32 gb sd card for my phone if that helps any. I forgot to mention that my phone is running Version 4.3 of the S4 software.
I am a total noob when it comes to these types of problems so please help me.
Do you know what firmware version you're on? Did you do a factory reset in recovery? Kies is junk you're probably going to have to use Odin. But even that may not work based on your description of the problems.
Sent from my Nexus 5 using XDA Free mobile app
Re:
jd1639 said:
Do you know what firmware version you're on? Did you do a factory reset in recovery? Kies is junk you're probably going to have to use Odin. But even that may not work based on your description of the problems.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I am running Version 4.3. I only installed Kies to make sure I had the right driver, but you're right, Odin doesn't see my phone. I did do a factory reset in recovery, hopefully I didn't completely screw myself.
Bulk like Hulk said:
I am running Version 4.3. I only installed Kies to make sure I had the right driver, but you're right, Odin doesn't see my phone. I did do a factory reset in recovery, hopefully I didn't completely screw myself.
Click to expand...
Click to collapse
If Odin the mk2 tar file, see the all in one from here
http://forum.xda-developers.com/showthread.php?p=49687770
What Windows os version are you using? Google 15 second adb install xda and try those drivers.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
If Odin the mk2 tar file, see the all in one from here
http://forum.xda-developers.com/showthread.php?p=49687770
What Windows os version are you using? Google 15 second adb install xda and try those drivers.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I'm running Windows 7. I'll try that when I get home. I'll let you know what happens.
jd1639 said:
If Odin the mk2 tar file, see the all in one from here
http://forum.xda-developers.com/showthread.php?p=49687770
What Windows os version are you using? Google 15 second adb install xda and try those drivers.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Sorry I haven't logged in for a while. This worked very well, thank you.:good:
ok, so I am not a noob on rooting and such, but this one has me stumped. Have the i337 on mdl baseband. Wanted to return it to stock. I tried to Odin (v3.09) the factory tar from the samsung site, i got a failure, then it went to recovery mode saying to connect kies. I have tried kies 2.6 and 3.0, neither recognize the device. I have tried redownloading samsung firmware thinking it was corrupted and mk2 firmwares in odin, neither worked, they go immediately to fail when i try to execute Odin. I can get into download mode or the kies recovery mode, not sure what to do since it will not take odin. Any ideas?
aawshads said:
ok, so I am not a noob on rooting and such, but this one has me stumped. Have the i337 on mdl baseband. Wanted to return it to stock. I tried to Odin (v3.09) the factory tar from the samsung site, i got a failure, then it went to recovery mode saying to connect kies. I have tried kies 2.6 and 3.0, neither recognize the device. I have tried redownloading samsung firmware thinking it was corrupted and mk2 firmwares in odin, neither worked, they go immediately to fail when i try to execute Odin. I can get into download mode or the kies recovery mode, not sure what to do since it will not take odin. Any ideas?
Click to expand...
Click to collapse
1. Kies and Recovery mode aren't same thing. Kies never will recognize your device being in Stock Recovery Mode. Don't mix things.
2. Find the error now is difficult coz maybe you update your bootloader with the MK2 firmware (that's android 4.3 no android 4.2.2).
3. Get me the errors or one screenshot that appears in ODIN when you try to flash the MK2 firmware pls.
I'll see what I can do, it happens so fast I don't think anything updates, and it shows me no errors, just fail
Sent from my SM-T320 using XDA Free mobile app
aawshads said:
I'll see what I can do, it happens so fast I don't think anything updates, and it shows me no errors, just fail
Sent from my SM-T320 using XDA Free mobile app
Click to expand...
Click to collapse
Maybe Kies was in your task bar when you tried to flash through ODIN?
Not the first but maybe the last ones, what does that do?
Sent from my SM-T320 using XDA Free mobile app
aawshads said:
Not the first but maybe the last ones, what does that do?
Sent from my SM-T320 using XDA Free mobile app
Click to expand...
Click to collapse
Close completely Kies before run ODIN and try again to flash the old bootloader. Tell me how works
Joku1981 said:
Close completely Kies before run ODIN and try again to flash the old bootloader. Tell me how works
Click to expand...
Click to collapse
ok, ran it, failed again, hereare the screenshots with the complete message portion.
aawshads said:
ok, ran it, failed again, hereare the screenshots with the complete message portion.
Click to expand...
Click to collapse
1. Try other version of ODIN. I recommend you the latest one -> HERE
2. And pls.... MK2 isn't firmware for your device, it's for i337M. Don't mix things. Flash MDL again if you had that baseband and show me what errors you will have in ODIN. Good luck
Still failed. Let me know what you see. thanks
Bump, anyone see what I is wrong?
Sent from my SM-T320 using XDA Free mobile app
aawshads said:
Bump, anyone see what I is wrong?
Sent from my SM-T320 using XDA Free mobile app
Click to expand...
Click to collapse
Are you sure you're on the mdl bootloader?
Sent from my Nexus 5 using XDA Free mobile app
Pit file
I see youre trying to flash the mk2 file but you dont have the pit file for the repartition head over here and download the mk2 pit file and then rerun it I also see that you have auto reboot checked, uncheck the auto reboot and then once iit finishes flashing and say reset unpluget you're device and pull the battery then put it back in and go into stock recovery by holding volume up power and home all at the same time and wipe data factory reset and cache partition http://d-h.st/5gz
Thanks, but that did not work either. I have never had a problem I couldn't odin out of, but I have tried everything I can think of and still nothing will work. I just want to sell the phone so I even tried the nb1 which should install no matter what bootloader I am on, and still nothing.
Hi, I am currently stuck where i was trying to download from 4.4.2 to 4.2.2 to unlock my phone. Currently Odin is not even downloading my phone 4.2.2 and i am stuck. I don't know what else i can try. Can somebody guide me through even if it starts from having a stock rom. I have went through many threads and spent hours searching. But have been unsuccessful.
Raj.R said:
Currently Odin is not even downloading my phone 4.2.2 and i am stuck.
Click to expand...
Click to collapse
What do you mean by this?
Buccanero said:
What do you mean by this?
Click to expand...
Click to collapse
Sorry, i mean the odin 3.09 is not even flashing the 4.2.2 rom into my phone. It says failed!
Raj.R said:
Sorry, i mean the odin 3.09 is not even flashing the 4.2.2 rom into my phone. It says failed!
Click to expand...
Click to collapse
If the sgh i337m is anything like the sgh-i337, then you can only downgrade to certain firmwares.
Why don't you try flashing a 4.2.2 modem in a custom recovery or Odin and using region regionlockaway. I'm not that familiar with the i337m but that works on the i337
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Why don't you try flashing a 4.2.2 modem in a custom recovery or Odin and using region regionlockaway. I'm not that familiar with the i337m but that works on the i337
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I just reflashing the stock 4.2.2 firmware and the screen stays on Samsung logo, don't go into main or anything. I don't know what i can do now. My phone seems to be bricked.
Raj.R said:
I just reflashing the stock 4.2.2 firmware and the screen stays on Samsung logo, don't go into main or anything. I don't know what i can do now. My phone seems to be bricked.
Click to expand...
Click to collapse
Can you boot into recovery? Do a factory reset there
Edit, also it can take a long time to boot after using Odin so make sure you give it enough time, 10 minutes
Sent from my Nexus 5 using XDA Free mobile app
to which firmwares, do u know?
I know how to do into downloading mode press all 3 buttons then vol up. But how do i go into recovery?
I gave it 15 minutes to boot last time. i'll give it 30 minutes this time.
i can make a cup of tea on my phone, it's that hot right now.
Can i get some support from somebody on how to unbrick my phone? Or how do i go into recovery mode to reinstall the firmware like one person mentioned here???
Raj.R said:
Can i get some support from somebody on how to unbrick my phone? Or how do i go into recovery mode to reinstall the firmware like one person mentioned here???
Click to expand...
Click to collapse
Can you get into download mode?. If so Odin the 4.4.2 firmware. You can get that at sammobile.com for your device.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Can you get into download mode?. If so Odin the 4.4.2 firmware. You can get that at sammobile.com for your device.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
ok thanks, i am doing to do it now. but the download takes soo long 4hrs..
While that gets downloaded, in the meantime, i am in recovery mode now, and i have the following options :
reboot system
apply update from adb
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache.
Did i miss any of these steps when i tried to downgrade the firmware to 4.2.2, is this where i messed up and bricked my phone?
Raj.R said:
ok thanks, i am doing to do it now. but the download takes soo long 4hrs..
While that gets downloaded, in the meantime, i am in recovery mode now, and i have the following options :
reboot system
apply update from adb
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache.
Did i miss any of these steps when i tried to downgrade the firmware to 4.2.2, is this where i messed up and bricked my phone?
Click to expand...
Click to collapse
Try wipe data/factory reset. That might get you post the bootloop
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Try wipe data/factory reset. That might get you post the bootloop
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
okay, did that and flashing now with odin.
okay, just booted up finally. now i can unlock my phone on 4.2.2 and then flash back to 4.4.2 or other firmwares.
Okay, so i just went through the Service mode menu to set the unlock. But i try put my sim in and it asks for sim unlock code?? I don't get it. what m i doing wrong?
can somebody help me pleaseeeeeeeeeeeeeeeeeeeeee
Ok i did it. CF root wasn't working so i tried kongo root and it did it;s magic and rooted my phone. So region away did it's job and unlocked my phone, immediately i got my fido signal on this bell phone. Next thing i am flashing 4.4.2 and then a custom rom with root access.