hi all, just this minute decided i want to try put Jelly Bean on my X8.
at the moment i have the stock android 2.1 that came with the phone. its rooted so i could use a custom launcher.
now firstly. if all failed or i wanted to restore the phone back to its original android 2.1, how would i do that? do i need to do a back up of the phone?
if so, how do i do this and what with.
now for the Jelly Bean rom. i want the best and most stable jelly bean rom that will not play up and work 100% including the camera.
which is the best jelly bean rom for my x8?
and how do i get the custom jelly bean rom on my x8.
bear in mind i have never done anything like this to my x8 before i could brick it as i dont have a clue what to do. so can someone give me the best noob guide or video that would be easy for a idiot to understand.
thank you to anyone who will help me
Dan.
Hey there. So now your phone is running rooted Android 2.1. First can you check the sticker behind you phone?(Turn off your phone and pull out the battery). Make sure the manufacturing date is below than 11W29. If it's above 11W29 you can't unlock your phone's bootloader and you can't install any JellyBean ROM. If it's below than 11W29 you can unlock your phone's bootloader using guides in this forum(Search unlock bootloader x8). After you have done unlocking the bootloader you now can proceed to installing custom kernel which is Oxydo-JB kernel or nAa-JB kernel using FlashTool. Then, you can flash MiniCM10 4.0.2 which is JellyBean ROM onto your device.
If you make any mistake during unlocking bootloader process it will result in hard brick. Make sure you follow the steps carefully. If you done everything correctly you can enjoy JellyBean on your phone. If you somehow managed to softbrick your device you can revived it using PC Companion or Flashtool. But it is better to make a backup in case something goes wrong.
Hope I helped you.
nazz.rule said:
Hey there. So now your phone is running rooted Android 2.1. First can you check the sticker behind you phone?(Turn off your phone and pull out the battery). Make sure the manufacturing date is below than 11W29. If it's above 11W29 you can't unlock your phone's bootloader and you can't install any JellyBean ROM. If it's below than 11W29 you can unlock your phone's bootloader using guides in this forum(Search unlock bootloader x8). After you have done unlocking the bootloader you now can proceed to installing custom kernel which is Oxydo-JB kernel or nAa-JB kernel using FlashTool. Then, you can flash MiniCM10 4.0.2 which is JellyBean ROM onto your device.
If you make any mistake during unlocking bootloader process it will result in hard brick. Make sure you follow the steps carefully. If you done everything correctly you can enjoy JellyBean on your phone. If you somehow managed to softbrick your device you can revived it using PC Companion or Flashtool. But it is better to make a backup in case something goes wrong.
Hope I helped you.
Click to expand...
Click to collapse
i believe you have gave me everything i need to get a custom rom on.
but one thing. how do i make a backup of my stock OS incase something goes wrong or i want to put the original back on?
how do i do it and what with? and where do i get the stock kernal and rom?
Vega_Dan said:
i believe you have gave me everything i need to get a custom rom on.
but one thing. how do i make a backup of my stock OS incase something goes wrong or i want to put the original back on?
how do i do it and what with? and where do i get the stock kernal and rom?
Click to expand...
Click to collapse
Here's the link to the stock 2.1 firmware. You have to flash this using FlashTool.
If you want to backup your stock ROM you have to install a recovery into your device. You can do this using x8toolbox. And after that, you can backup the stock ROM using the recovery.
nazz.rule said:
Here's the link to the stock 2.1 firmware. You have to flash this using FlashTool.
If you want to backup your stock ROM you have to install a recovery into your device. You can do this using x8toolbox. And after that, you can backup the stock ROM using the recovery.
Click to expand...
Click to collapse
will that work for a UK phone because it says Greek on it.
Vega_Dan said:
will that work for a UK phone because it says Greek on it.
Click to expand...
Click to collapse
It should work. I've tried it with my phone and it works. But I only use it for an hour,though.
If you want back stock 2.1 , use Sony PC Companion.
Sent from my E15i using xda app-developers app
i have knocked this on the head and gave up.
i unlocked the bootloader and flashed the kernel. but when i tried installing jellybean i just get a failed to install and a (status 7) error everytime i tried.
i tried reflashing the kernel. i tried 5 or so different roms including a few ICS ones and still got the same problem.
so i have now just put the stock 2.1 OS back on.
Vega_Dan said:
i have knocked this on the head and gave up.
i unlocked the bootloader and flashed the kernel. but when i tried installing jellybean i just get a failed to install and a (status 7) error everytime i tried.
i tried reflashing the kernel. i tried 5 or so different roms including a few ICS ones and still got the same problem.
so i have now just put the stock 2.1 OS back on.
Click to expand...
Click to collapse
If I'm not mistaken, status 7 error is because corrupted zip file. Have you tried redowloading the ROM.zip file and check the MD5 sum?
Sent from my Xperia™ X8
nazz.rule said:
If I'm not mistaken, status 7 error is because corrupted zip file. Have you tried redowloading the ROM.zip file and check the MD5 sum?
Sent from my Xperia™ X8
Click to expand...
Click to collapse
surely all 5 or 6 of them roms shunt have corrupt. plus I had downloaded one of them 3x and was still same.
@Vega_Dan
If you get Status 7, do this:
1. Open up the ROM.zip file.
2. Open up updater-script from META-INF>com>google>android.
3. Remove the first few getprop lines.
4. Save it and try flashing now.
Hope this helped.
It happens a lot on my kernel.
Vega_Dan said:
i have knocked this on the head and gave up.
i unlocked the bootloader and flashed the kernel. but when i tried installing jellybean i just get a failed to install and a (status 7) error everytime i tried.
i tried reflashing the kernel. i tried 5 or so different roms including a few ICS ones and still got the same problem.
so i have now just put the stock 2.1 OS back on.
Click to expand...
Click to collapse
before installing go to advanced and format system,data,cache.
Sent from my E15i using xda app-developers app
Lukenda said:
before installing go to advanced and format system,data,cache.
Sent from my E15i using xda app-developers app
Click to expand...
Click to collapse
tried all that.
sgt. meow said:
@Vega_Dan
If you get Status 7, do this:
1. Open up the ROM.zip file.
2. Open up updater-script from META-INF>com>google>android.
3. Remove the first few getprop lines.
4. Save it and try flashing now.
Hope this helped.
It happens a lot on my kernel.
Click to expand...
Click to collapse
wish i knew that then. i cant be bothered now to go through it all again. it was giving me a headache.
ive only just finished getting my phone back to how it was before i started.
i may have a go sometime next week.
thanks for that.
so ive just reflashed the oxydo-jb kernel. now I have removed a few lines from the zip file and get a status 6 error.
I don't know if I have removed the right bits or not.
success guys. its seems it was the oxydo-jb that was the problem because I have used the nAa-JB kernel and its worked.
I now have MINI CM10 JB now.
Related
I just bought my Epic 4G a few days ago and quickly discovered the existence of rooting and custom ROMS. Needless to say I took the plunge the other day.
I attempted to install the Epic Experience Froyo yesterday but it doesn't seem to load up properly.
Seemed simple enough. I boot into clockwork, I cleared data/factory cache, cache partition, and davnik cache three times each. I installed the ROM from my SD card, install says it's successful, so I hit the reboot.
After this I expect my new rom to load up but all that happens is the samsung logo comes up for about a minute, phone reboots again and goes into the factory Android system recovery utility.
Any ideas? Please help, my phone is inoperable at the moment.
-Dennis
Sounds like kernel. Dl a costume kernel and flash it thru cwm.
Sent from my SPH-D700 using Tapatalk
I'll have to apologize ahead of time because I'm completely new to rooting.
Which kernel should I use (a link to one with instructions would be helpful), and how do I get it on my SD card if it isn't booting up? (my pc doesn't have an SD card reader)
Did you first use odin to install the DK17 modem and kernel through odin? That might be the step youmissed because if you just flashed straight from stock 2.1 to epic experience you need the updated froyo modem and kernel. Check here if you're still confused.
http://forum.xda-developers.com/showthread.php?t=853209
So, flash Odin/DK17 and then flash Epic Experience over this?
Ya also did you first do the one click root method to make sure you are definitely rooted? If you press. Volume down + camera button + power when booting and the letters are blue you are NOT rooted. If they are green then you are rooted. Sometimes when you install a rom it might take away your root so you might try doing it in the order of this:
1. Flash back to stock 2.1
2. Do theone click root method
3. Flash DK17 modem through odin
4. Install Epic Exprience
hgvidal said:
Did you first use odin to install the DK17 modem and kernel through odin? That might be the step youmissed because if you just flashed straight from stock 2.1 to epic experience you need the updated froyo modem and kernel. Check here if you're still confused.
http://forum.xda-developers.com/showthread.php?t=853209
Click to expand...
Click to collapse
I went straight from 2.1 to 2.2 firmware without using odin or anything of the sort. Will I notice a difference? If so what difference will it make and can I just install DK17 modem and kernel or do I have to revert back to 2.1 first?
idontwanttostudy said:
I went straight from 2.1 to 2.2 firmware without using odin or anything of the sort. Will I notice a difference? If so what difference will it make and can I just install DK17 modem and kernel or do I have to revert back to 2.1 first?
Click to expand...
Click to collapse
Hm that is interesting. When i first made the mistake of going from to a 2.2 rom without upgrading the modem my cell & data service wouldn't work. It kept looping on and off and would not stick. Maybe it depends what rom you went to as maybe some require the modem as mandatory and others do not? I am not sure. But if its working for you, you should just be able to flash the DK17 through odin without going back to 2.1.
hgvidal said:
Hm that is interesting. When i first made the mistake of going from to a 2.2 rom without upgrading the modem my cell & data service wouldn't work. It kept looping on and off and would not stick. Maybe it depends what rom you went to as maybe some require the modem as mandatory and others do not? I am not sure. But if its working for you, you should just be able to flash the DK17 through odin without going back to 2.1.
Click to expand...
Click to collapse
I just did it today with the newest froyo version out by chance would it come with them? If not where can i get them? I cant seem to find the modem to dl
How can i tell by looking in my phone if i have it or not?
idontwanttostudy said:
How can i tell by looking in my phone if i have it or not?
Click to expand...
Click to collapse
Go to settings -> about phone and then check where it says "Baseband version" it should say DK17 in there. If it doesnt follow these instructions to download the files you need. It has step by step directions
http://www.nomie.mobi/how-to-install-dk17-modem-samsung-epic/
I assume this is the rom you flashed:
http://forum.xda-developers.com/showthread.php?t=856715
In the first post it has a link to the instructions to properly flash the rom. You can use those instructions to flash the modem and see if it fixes your problem. You might be better off just flashing everything again. It would mean downloading odin and the files to your pc and flashing them to your phone from your pc. The simplest way to do this is follow this thread
http://forum.xda-developers.com/showthread.php?t=853209
Follow the instructions carefully and when your done you have the new modem, the froyo rom, clockwork recovery, and be rooted.
I was at the site earlier but when i click the dl link it takes me to some wordpress and tells me registration is currently not allowed then asks for a username and password
@Raylusk can i do this method even if i am running the 2.2 firmware? Or would i have to revert back to the original is so how do i do it?
idontwanttostudy said:
I was at the site earlier but when i click the dl link it takes me to some wordpress and tells me registration is currently not allowed then asks for a username and password
@Raylusk can i do this method even if i am running the 2.2 firmware? Or would i have to revert back to the original is so how do i do it?
Click to expand...
Click to collapse
You can do it running 2.2. This will wipe your phone and install the new system.
Sent from my SPH-D700 using XDA App
raylusk said:
You can do it running 2.2. This will wipe your phone and install the new system.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Ok I finally have it all worked out thanks a lot!
hgvidal said:
1. Flash back to stock 2.1 [through odin]
3. Flash DK17 modem through odin
4. Install Epic Exprience
Click to expand...
Click to collapse
I actually skipped step 2 and everything went fine for me. My laptop was being an asshole and not seeing the phone, so the 1 click root script simply wasn't working.. but then I realized that the DK17 flash via Odin that I got form the epic experience thread included clockworkmod and was pre-rooted and everything so I saw that step as unnecessary.
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,
My warranty has just run out on my Nexus One so I've decided to unlock the bootloader.
My Aim is to get from stock non rooted Gingerbread to rooted Gingerbread with busybox, SU, and ultimately being able to boot into ubunto in chroot, I've been reading up on all this for a few days now but just need a small amount of help with Recovery, Gingerbread ROM choice, and the order that thing should be done, by someone who's done this before.
I take it the first thing is to install SDK and get The USB Driver working on PC, its running XP by the way.
Then I unlock the bootloader, !HELP! to do this do I enter hboot or fastboot, before connecting the phone to the PC? I have to copy 3 files somewhere and use ADB and run command for **** OEM unlock, can't remember the exact command, (I've got instructions for this) and then agree to void my warranty etc.
I then find and download the correct custom recovery image and copy this into the tools folder of the SDK. And install (got instructions for this to).
!HELP!
Which custom recovery image should I use? and which Rooted Gingerbread ROM is most popular ?
After installing the custom Recovery can I just flash a custom ROM? I've seen something about SU.zip mentioned, is this necessary?
If I can just flash a custom ROM, I do this by downloading and copying the custom ROM of choice to the root of my SD card. Start phone in recovery mode and install from SD? I then install the google add ons .zip (if required) using the same method.
Sorry for such a long post and so many questions but I can find all the information for what I'd like to achieve but not in one place and nowhere in any chronological order.
Any advice appreciated .
Please read the Wiki, "Root" guides, "Unlock bootloader and install custom ROM" thread. Execute until the point of installing custom ROM.
Look in "Recovery" section for recoveries, install the latest Amon_RA.
Ive Successfully Rooted Gingerbread by following this method http://chensun.net/android-development/root-nexus-one-with-android-2-3-3-gingerbread/8/
GB ROM
Im running CM7RC4 and am happy w/ it
MouseIdt said:
Ive Successfully Rooted Gingerbread by following this method http://chensun.net/android-development/root-nexus-one-with-android-2-3-3-gingerbread/8/
Click to expand...
Click to collapse
Thanks everyone, but this looks like the one for me, going to unlock bootloader now install custom recovery and flash su.zip.
I'll post back with how I went on. Wish me look
A apprehensive newbie ;-)
Flash this as well, otherwise you will lose your custom recovery...
http://db.tt/cp7De8G
Sent from my Nexus One using XDA Premium App
Good show with unlocking the bootloader, it's the best way.
However... looking at your flag, you're in the UK... this means your phone is still in warranty, as we get 24 months.
Nooooo
Rusty! said:
Good show with unlocking the bootloader, it's the best way.
However... looking at your flag, you're in the UK... this means your phone is still in warranty, as we get 24 months.
Click to expand...
Click to collapse
My understanding was 12 months but, your probably right. I've unlocked the bootloader now and fortunately my N1 is in good condition, funtioning correctly ( well at least for now, I'll have to cross that bridge if and when I get to it )
Getting on to custom recovery, I realised something wasn't quite right after my first attempt. I installed custom recovery but without su.zip on my SD card. I managed after rebooting my PC to complete the custom recovery with su.zip on the SD card and was successful in that I've got SU on my N1. However I am quite sure I do need to fix something with the recovery, can someone explain what method or how I do this now. I've unlocked the bootloader, I am rooted with gingerbread but with a dodgy recovery.
Or do I do exactly the same as I did with su.zip and push recovery from ADB and flash from SD card, making sure that fix-recovery.zip is indeed on the SD card.
Hope this makes sence?
Any help appreciated.
After I unlocked my n1 I used rom manager for everything else, first flashing clockwork mod, then selecting a stable cm 7 build and flashing that, since then I've done everything through recovery, flashing custom kernels and nightlie builds, I'm currently using cm7 rc4 highly recommend rover theme too!
Sent from my Nexus One using XDA Premium App
sparkyryan said:
After I unlocked my n1 I used rom manager for everything else, first flashing clockwork mod, then selecting a stable cm 7 build and flashing that, since then I've done everything through recovery, flashing custom kernels and nightlie builds, I'm currently using cm7 rc4 highly recommend rover theme too!
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
I've got ROM Manager installed and if I want to try anything it tells me I have to flash clockwork mod recovery, I was unsure if It was safe to do this after using a completely different recovery image to get where I am now.
Sorry for being such a paranoid newbie, but we all got to start somewhere ;-)
sparkyryan said:
After I unlocked my n1 I used rom manager for everything else, first flashing clockwork mod, then selecting a stable cm 7 build and flashing that, since then I've done everything through recovery, flashing custom kernels and nightlie builds, I'm currently using cm7 rc4 highly recommend rover theme too!
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
I think CM7 rc4 is next, I do want to get Linux up and running though, even if it's in a virtual environment (chroot). and deffinately would like to check some nice themes out, I've not even looked at themes yet, I suppose it's quite easy after unlocking bootloader, installing custom recovery then flashing su.zip though. But still any pointers where to start my quest wouldn't go a miss ;-)
Recovery
its safe to let rom manager flash clockwork,ive done it
I heared about amonRA but it seemed like clockworkmod was more commonly used so I went for that, but yeah it's fine to flash a new recovery, just remember that whilst it's rare things can go wrong, it's YOUR fault not anyone's here regardless of the advice you may get here if your phone gets bricked or screwed up.
That said I'm still new to this but I'm learning as I'm going, just remember to backup your phone using rom manager before doing anything major so that you can always recover your phone/rom.
I started out hacking my nokia 5800 so was keen to have a go with the android platform.
Sent from my Nexus One using XDA Premium App
CM7 stable
Have you upgraded to cm 7 stable? its a definate upgrade
**UPDATED**
If you experience RANDOM reboots across different ROMS, and KERNELs, you've come to the right place!! You can solve this issue using the steps described below.
Apparently this is caused by some misconfiguration. Something went terribly wrong and is owning your phone randomdly... So we have to go back to stock and run the phone once to solve any issues.
(I spend a lot of time trollin' devs and other users to give me further info about it, but it ended out being a problem of my phone.) :S
So, to solve this, you'll need to flash 2 things using flashtool:
1- stock 2.1.1.A.0.6 ROM,
2- baseband: 2.1.1.A.0.6 BASEBAND 15 (IMPORTANT: choose the correct one (e15i or e15a) depending on your hardware!!!, check the label below your battery or you'll get F!-up)
download here (thanks lucastan96 for this link)
Note: The following procedure will not RE-LOCK the loader, so relax!
8 steps to glory: follow the order or you'll get served.
1. turn off the phone and format your SD card elsewhere
2. flash stock ROM
3. flash the baseband
4. turn on the phone and go through the setup once
5. turn off the phone and format the SD card elsewhere
6. copy the ROM you wish to install in your SD card
7. flash a CWM kernel and install the ROM (.zip) (make a factory reset before installing!!)
7.1. (optional) if you choose a stock rom kernel, turn off the phone and flash THE BASEBAND
8. turn on the phone and enjoy.
regards
Facepalm* this is stock ROM...i need a fix for MiniCM 3.0.0
Sent from my E15i using xda premium
ElmirBuljubasic said:
Facepalm* this is stock ROM...i need a fix for MiniCM 3.0.0
Sent from my E15i using xda premium
Click to expand...
Click to collapse
You didn't understand, seems to me.
You have to do all this steps in order to make your phone alright and after that you can flash any ROM you wish and your random reboot problem should be solved.
ElmirBuljubasic said:
Facepalm* this is stock ROM...i need a fix for MiniCM 3.0.0
Sent from my E15i using xda premium
Click to expand...
Click to collapse
Facepalm* You didn't read the instructions correctly.
First you flash everything stock; hopefully fixing the random reboots and then:
"7. copy the ROM you wish to install in your SD card"
in your case; MiniCM 3.0.0
---
Top Tip:
*Next time, try not to be so rash and avoid embarrassment.
Mhhh ... I did everything! But it did not work
I also have problem with random reboots on minicm7 (purple LED and then reset).
Anyone can confirm if it works?
@slake84: Almost 100% sure that's a Custom Kernel BUG.
This thread is for those having RANDOM REBOOTS/crashes using different ROMS AND KERNELS.
Thanks mate, it works :good:
Nton'S said:
Thanks mate, it works :good:
Click to expand...
Click to collapse
Sorry after almost two days without random reboot today the problem come back again, any other solution please?
I was 4.3 (locked bootloader) and the phone worked fine until one instance where the lcd glitched in the messaging app and it stopped responding. So I hard reset the phone and then it got stuck at the nexus logo (Bootloop).
So, i tried the following things:
1) Unlock bootloader
2) Flash 4.4 (KRT16S) from fastboot. Flash completed successfully, there were NO errors. Waited for a while, still stuck in the nexus circling logo. So i went to recovery and wiped data and cache, rebooted and waited for atleast 30mins.
3) Next, I tried 4.3 (jwr66y). Went through the same drill, still not booting. At this point I starting looking online to see if others are having the same problem. This is probably close to what I could find (http://www.reddit.com/r/nexus4/comments/1nefzy/)
4) Lastly I flashed 4.2 (jdq39) using the same procedure as the last 2, but this time it boots successfully! I cannot explain why, I have not done anything different this time.
So I thought I'll give 4.4 another try, but it doesnt work. Stuck in a bootloop. Immediately I flashed back 4.2. So, ultimately only 4.2 works on this phone for some reason. Any ideas as to why this is happening?
Is there a hardware problem with the nandflash, if so how do I verify it?
Also I did not use the toolkit to flash, I just ran flash-all.bat and verified that each command was executed successfully.
UPDATE: This is a rare problem that has affects a handful nexus 4s. The best option is to RMA the phone if it is under warranty of sell the phone for parts. This post gives a good summary of the problem: http://forum.xda-developers.com/showpost.php?p=47532787&postcount=282
jblack248 said:
I have the unknown IMEI and baseband problem that I've seen a number of people have without resolution. While I appreciate the efforts made here, I am including myself in the group that this unbricking method did not work for. For the sake of hoping to save other people time, I'm going to write out my experiences with this problem so far.
I was running CM 10.2 nightly 20131114 without issue when after a reboot my phone bootlooped on the starting animation. I've had errors on nightlies before, so I did the normal routine of fixes. I tried everything from restoring nandroid backups, flashing newer and older radios, doing a fresh install of a known working CM build, then wiped the entire device and tried flashing factory images for 4.4 and 4.3. None of these got the device to boot. Based on a recommendation I went back to the 4.2 factory image and had some luck, but it took a very long time to boot and had an unknown IMEI and baseband. It took a very long time to boot with or without the SIM card.
At this point I tried the unbrick method listed here, and when I restored the factory image I had the exact same problem. I applied the 16 GB fix, but since I'm going to give up for the RMA long-haul I'm not even bothering with the MAC address fixes. I'm restoring to the 4.2 factory image and locking the bootloader so I can send this device back to Google / LG.
I haven't seen anyone recover from the unknown IMEI and baseband problem, and it's scary because it happens for no reason on both stock and custom ROMs. I really like my Nexus 4, but it's going to be hard to trust whatever replacement I get (if any) from Google / LG.
Click to expand...
Click to collapse
@pravarth It looks like you flashed the wrong image to the nexus 4. Always flash image which says occam (thats the codename) . If 4.2 works then surely 4.3 and 4.4 will work successfully.
Always downlaod image from here :
HTML:
https://developers.google.com/android/nexus/images#occam
.
Just flash 4.4 again and see .
Abhiheart said:
@pravarth It looks like you flashed the wrong image to the nexus 4. Always flash image which says occam (thats the codename) . If 4.2 works then surely 4.3 and 4.4 will work successfully.
Always downlaod image from here :
HTML:
https://developers.google.com/android/nexus/images#occam
.
Just flash 4.4 again and see .
Click to expand...
Click to collapse
I got the images from that link and I also double checked that I'm using occam images
occam-jdq39-factory-345dc199 (4.2)
occam-jwr66y-factory-74b1deab (4.3)
occam-krt16s-factory-2006f418 (4.4)
I also verified the md5 hash on all 3. The files are fine
@pravarth : You are on unlocked bootloader, try flashing a 4.4 custom ROM and see
Flash This :
HTML:
http://forum.xda-developers.com/showthread.php?t=2507021
nice
Sent from my Micromax A250 (CanvasTurbo) using XDA Premium 4 mobile app
hmm, the factory images should work. are you under warranty?
same case, my phone only works with 4.2
amartinpascual said:
same case, my phone only works with 4.2
Click to expand...
Click to collapse
Really farfetched but maybe something got damaged in persist or one of the other partitions. If you can figure out a way of enabling usb debugging in 4.3/4.4 (say enabling it in 4.2 and dirty flashing system/boot or maybe flashing a custom rom that has it enabled by default), you might be able to investigate further with logcat.
ziddey said:
Really farfetched but maybe something got damaged in persist or one of the other partitions. If you can figure out a way of enabling usb debugging in 4.3/4.4 (say enabling it in 4.2 and dirty flashing system/boot or maybe flashing a custom rom that has it enabled by default), you might be able to investigate further with logcat.
Click to expand...
Click to collapse
Logcat?
Abhiheart said:
@pravarth : You are on unlocked bootloader, try flashing a 4.4 custom ROM and see
Flash This :
HTML:
http://forum.xda-developers.com/showthread.php?t=2507021
Click to expand...
Click to collapse
Don´t works, same bootloop
Wrong bootloader?
Sent from my Nexus 4 using xda app-developers app
ziddey said:
hmm, the factory images should work. are you under warranty?
Click to expand...
Click to collapse
Yes, I'm under warranty but I bought the phone from USA and I don't want to send it back unless I have to. So I'm trying all options
Oxious119 said:
Wrong bootloader?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
The appropriate bootloader and radio images were flashed before flashing the image.
According this thread, it seems the problem exists with baseband and apparently is a known problem (http://forum.xda-developers.com/showthread.php?p=48332273#post48332273). So it seems only .48 baseband boots. This is probably what is happening with mine as well. I'll check if they work while on .48 baseband
same problem, like this: http://forum.xda-developers.com/showthread.php?p=48332273#post48332273
tip: you can use 4.3, flash 4.3, then flash the radio of 4.2.2: cwm-radio-mako-m9615a-cefwmazm-2.0.1700.48
but this tip didn't work with 4.4 or 4.4.1, i'm also looking for a solution
Abhiheart said:
@pravarth : You are on unlocked bootloader, try flashing a 4.4 custom ROM and see
Flash This :
HTML:
http://forum.xda-developers.com/showthread.php?t=2507021
Click to expand...
Click to collapse
I tried flashing CM10.2, stuck in bootloop
So, I've found quite a few threads with the same problem and no solution. http://forum.xda-developers.com/showthread.php?t=2525479
http://forum.xda-developers.com/showthread.php?t=2450301
4.2 boots but imei and baseband in settings shows unknown. In bootloader mode the radio version is shown.
jedivulcan said:
Same thing happened to me yesterday. I turned the phone on and it was in a persistent bootloop. Tried everything to get it working until I flashed 4.2.2 and then there was no IMEI or baseband.
Click to expand...
Click to collapse
flash the radio cwm-radio-mako-m9615a-cefwmazm-2.0.1700.48
:/ so this is another problem, good job google! someone have tried to flash the 0.98 radio with 4.4.1/2?
pravarth said:
I tried flashing CM10.2, stuck in bootloop
So, I've found quite a few threads with the same problem and no solution. http://forum.xda-developers.com/showthread.php?t=2525479
http://forum.xda-developers.com/showthread.php?t=2450301
4.2 boots but imei and baseband in settings shows unknown. In bootloader mode the radio version is shown.
Click to expand...
Click to collapse
@pravarth : Did you try factory reset ?? try that might fix your IMEI and baseband
I had a similar issue trying to flash the factory 4.3 and 4.4 images. Everything appeared to flash successfully, but it would never get past the boot logo.
I don't recall where I found it, but someone said to try re-locking then unlocking the bootloader. It worked for me. Maybe it could work for you.
rsilvawashington said:
I had a similar issue trying to flash the factory 4.3 and 4.4 images. Everything appeared to flash successfully, but it would never get past the boot logo.
I don't recall where I found it, but someone said to try re-locking then unlocking the bootloader. It worked for me. Maybe it could work for you.
Click to expand...
Click to collapse
doesn't work
The "no baseband" thing sounds like that old recovery bug. Are you using the latest twrp or cwm?
Sent from my Nexus 4 using xda app-developers app
at4r1 said:
The "no baseband" thing sounds like that old recovery bug. Are you using the latest twrp or cwm?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
The problem started when i was on stock ROM with stock recovery. It has nothing to do with twrp or cwm in this case