Related
These are the steps i took to get back to the Stock bell rom. I take no credit for this method, NFHimself made the scripts, and mods for deodexing.
This takes an hour at least.. Make sure your battery is FULLY charged, Do a backup first as well to save your sd card contents.. You have to do a factory reset after the process is complete.
1)reinstall a fresh sbf of the french 2.1.1 and login to motoblur. French sbf can be found in this thread, Close to the bottom of the page.
2) enable usb debugging.. menu, settings, applications, development, then check usb debugging
3) go to NFHimselfs deodex/mod thread here
4)download Version 9, and extract it to your computer
5)Run the menu.bat file
6) choose the root option. and follow the instructions. If it doesn't complete successfully, unroot and try again. Took me a couple times to get my phone rooted properly.
7) once root is complete, choose restore phone. This will automatically download the files needed to get you back to the stock rom. It will take a little bit of time to download, so have a drink or smoke or something.
The restore will take an hour or so to complete. Be patient.
I got to the point where it said waiting for phone to shutdown, so i pulled the battery and did it manually. Once my phone booted back up again, it was on the stock bell rom.
Thanks to all who helped me! Y2whisper and kieller from the support.motorola forums.
Don't forget to thank NFHimself.
NOTE: I had to do a factory reset to get the Market app back.
I managed to get the bell update with no problems!
right on I was wondering how I would get back to the stock Bell.....I'm running the French 2.1.1, so when the time comes I can sit back for an hour or so and bring the phone back to stock...........yaaaahoooo......
nate_benji were you on the french 2.1.1 before you did this?? cause I'm on 2.1.1 and I am rooted, just wondering if I have to do all over... flashing 2.1.1 again and root??? but I guess it can't hurt with a fresh install......guess I'm getting lazy in my old age...lol
dillfever said:
nate_benji were you on the french 2.1.1 before you did this?? cause I'm on 2.1.1 and I am rooted, just wondering if I have to do all over... flashing 2.1.1 again and root??? but I guess it can't hurt with a fresh install......guess I'm getting lazy in my old age...lol
Click to expand...
Click to collapse
Yes, i was on the french 2.1.1. The only reason i did a fresh install of the french 2.1.1 sbf is because the rooting method is a little different than using gingerbreak. I tried with a normal root, but it didn't work. NFHimself's mod/deodex application has the root option built in. That's what I used, and it worked well.
What's the benifit over the french 2.2.1 ???
YBrazeau said:
What's the benifit over the french 2.2.1 ???
Click to expand...
Click to collapse
The new update, I presume.
If I get bored between now and an international release or leak of GB then perhaps I'll give this a shot too. Thanks for sharing it, guys! Great work as always.
YBrazeau said:
What's the benifit over the french 2.2.1 ???
Click to expand...
Click to collapse
The benefit is you get the bell updates, who knows when the other carriers will release the gingerbread updates. Mind you bell is slow at releasing anything..
Sent from my MB860 using XDA App
Thanks nate, then when the time comes that's exactly what I shall do......
The biggest benefit of this would probably be that when you do this it would be really hard to tell if you ever modded the phone. Also Bell is likely to get the Gingerbread update before people in Europe.
I am doing a restore and got a tar crc error and a error on restoring mmcblk0p3 - should i wait till it finish .....i don't like the the crc error..thanks 1 done cat /data/local... ! bus error shsu (no boot) failed to boot 2 ...starting rsd mode, reflashing now...anyone know why there is a crc fail..
Could it be possible to get a direct link to the French 2.2.1 sbf, this way everything needed is in one location?
Thanks
capercb said:
I am doing a restore and got a tar crc error and a error on restoring mmcblk0p3 - should i wait till it finish .....i don't like the the crc error..thanks 1 done cat /data/local... ! bus error shsu (no boot) failed to boot 2 ...starting rsd mode, reflashing now...anyone know why there is a crc fail..
Click to expand...
Click to collapse
I am having this exact same issue. Is the mmcblk0p3 file that is included within the backup_OLYLA_U4_0.37.4.tar.gz that NFHimself posted possible corrupt?
davisx said:
I am having this exact same issue. Is the mmcblk0p3 file that is included within the backup_OLYLA_U4_0.37.4.tar.gz that NFHimself posted possible corrupt?
Click to expand...
Click to collapse
I don't think so. i did it from a fresh flash of 2.1.1 and it worked fine. you just have to make sure you rooted using his scripts. that was a problem i was having using his app before i used these scripts.
capercb said:
I am doing a restore and got a tar crc error and a error on restoring mmcblk0p3 - should i wait till it finish .....i don't like the the crc error..thanks 1 done cat /data/local... ! bus error shsu (no boot) failed to boot 2 ...starting rsd mode, reflashing now...anyone know why there is a crc fail..
Click to expand...
Click to collapse
I had that too i believe. Not sure why mmcblk03 failed, but all the rest passed for me. Did you re-sbf and try it again?
fearthefox said:
Could it be possible to get a direct link to the French 2.2.1 sbf, this way everything needed is in one location?
Thanks
Click to expand...
Click to collapse
I updated the original post, with a link to another thread that has a list of all known atrix sbf's. The french one is close to the bottom of the list.
Is this the one you are referring to...
Branding: Retail France
Version: 2.1.1 Full
Android Version: 2.2.2
Bootloader Version: N/A
Webtop version: N/A
Requires RSD Lite 5.0.0
Requires Moto Android (De)packer 1.3 to edit.
As you opening post says french 2.2.1 and I cannot find that on the page you linked to.
nate_benji said:
I had that too i believe. Not sure why mmcblk03 failed, but all the rest passed for me. Did you re-sbf and try it again?
Click to expand...
Click to collapse
Ya I got it but really weird ..notice when the program expands there is no mmcblk03 in the file also when it finish it keep coming up as timeout so I removed it from usb and pulled out the battery restarted and dl the update..It seems like a good update so far..ty
Sent from my MB860 using XDA App
Hi,
I removed partition 3 from the backup, it's your Motorola pds partition, it's not necessary to get back to stock, there are no sbf files that overwrite it. I also updated the atrix mods app to not reference partition 3.
Cheers!
NFHimself said:
Hi,
I removed partition 3 from the backup, it's your Motorola pds partition, it's not necessary to get back to stock, there are no sbf files that overwrite it. I also updated the atrix mods app to not reference partition 3.
Cheers!
Click to expand...
Click to collapse
Awesome! Thanks for creating the scripts, and the app. Made it possible to get me back to the stock bell rom, without a cwm backup. Now that reminds me, time to root, install cwm and do a backup!
Thanks again NFHimself..
fearthefox said:
Is this the one you are referring to...
Branding: Retail France
Version: 2.1.1 Full
Android Version: 2.2.2
Bootloader Version: N/A
Webtop version: N/A
Requires RSD Lite 5.0.0
Requires Moto Android (De)packer 1.3 to edit.
As you opening post says french 2.2.1 and I cannot find that on the page you linked to.
Click to expand...
Click to collapse
Sorry thats a typo, it should be 2.1.1
I have a AT&T Version of the Nexus S. I updated to 2.3.6 and it killed my radio signal, not as in low, as in an X above the signal bars. So i then went on to pushing the old radio back to the phone. When i pushed the old radio, not only did it not fix my signal issue. It has killed my WiFi, under settings the WiFi just says error. Been without a phone for almost two weeks trying to fix this any help would be great!
Here is my phone info as under settings:
Model Number: Nexus S
Android Version: 2.3.6
Baseband Version: I920XXKB3
Kernel Version: [email protected]#14
Build Number: GRK39F
Thanks!
tried others radio ? KF1 KB3 KD1 ...etc ?
WIFI error , i usually experienced that when i flash new kernel , so ...
you may solved it by flash other kernel
qtwrk said:
tried others radio ? KF1 KB3 KD1 ...etc ?
WIFI error , i usually experienced that when i flash new kernel , so ...
you may solved it by flash other kernel
Click to expand...
Click to collapse
Yup have pushed multiple radios, with no luck. In not sure about the Kernel unless it was updated with 2.3.6 roll out. I haven't updated it, just driving me nuts.
well ...
if i were you , i would try wipe and format everything on the phone , of course , back up first , and then flash whole new stock ROM ... try it out
---------- Post added at 11:00 PM ---------- Previous post was at 10:59 PM ----------
RSuksdorf said:
Yup have pushed multiple radios, with no luck. In not sure about the Kernel unless it was updated with 2.3.6 roll out. I haven't updated it, just driving me nuts.
Click to expand...
Click to collapse
Kernel Version: [email protected]#14
obviously your kernel is not a stock one ...
I've run into this problem flashing an anykernel script kernel separately from a rom, as in flashed rom, booted up, then cwn again for kernel. Instead of all in one cwm session.
Sent from my Nexus S 4G using Tapatalk
Flash the KB3 Radio because I have AT&T
If you don't have Root explorer Go into the web via wifi : 4shared.com
Download 'Root Explorer v.2.16"
Open it accept super user request
Go into EFS File And
Long Press/Move To Root Of SD the Following Files:
Nv.log
Nv_data.bin
Nv_data.bin.md5
Reboot phone and your Phone will be back to normal =]
Btw even if u move the files to Root Of SD ..once u reboot ull have them back in the EFS file and now in Root Of SD. But "REMEMBER" Flash KB3 Radio First! . Can't find it? go into Nexus S Development. .. scroll down til u see the Radio Thread
=]
Update: Just Noticed ur already on KB3 ... flash UCKD1 then follow the Steps.. then flash KB3 Again ^_^
-Sent While Motor boating Your Mom =D
Having a similar issue. I got stuck with a bootloop and even after flashing the latest stable clockwork recovery and CM7 release it still would not exit the boot loop. i wiped the cache/dalvik...still no bueno. i decided to wipe the entire device.
i was able to reinstall all my apps that i needed but the wifi status remains listed at "error".
i rebooted the phone, even tried the steps mentioned previously:
*backed up the efs_backup.bat / efs_backup.sh by running adb pull /efs
*using Root Explorer, i didn't have the "Nv.log" file in my /efs folder. I was able to move the Nv_data.bin & Nv_data.bin.md5 files to the /sdcard folder.
I rebooted the device but the issue remains.
Which radio version do I have because the ones i saw on the guide does not list an I9020XXJK8..unless the remaining characters after i9020 are supposed to equal one of the I9020a/I9020t/I9023 versions....
My phone's information:
android version: 2.3.7
baseband: I9020XXJK8
Kernel: [email protected] #5
Mod Version: CyanogenMod-7.1.0.1-ns
build number: cyanogen_crespo-eng 2.3.7 GINGERBREAD eng.kalimochoaz.20111019.184032 test-keys
Click to expand...
Click to collapse
I've also tried an advanced restore of the boot from a back up (from June 2011). rebooted the device and now it wont even get past the google screen w/ the unlock symbol.
i tried another restore of the backup from a recent date and i was able to get back into my phone but the issue remains.
headsh0tshurt said:
Having a similar issue. I got stuck with a bootloop and even after flashing the latest stable clockwork recovery and CM7 release it still would not exit the boot loop. i wiped the cache/dalvik...still no bueno. i decided to wipe the entire device.
i was able to reinstall all my apps that i needed but the wifi status remains listed at "error".
i rebooted the phone, even tried the steps mentioned previously:
*backed up the efs_backup.bat / efs_backup.sh by running adb pull /efs
*using Root Explorer, i didn't have the "Nv.log" file in my /efs folder. I was able to move the Nv_data.bin & Nv_data.bin.md5 files to the /sdcard folder.
I rebooted the device but the issue remains.
Which radio version do I have because the ones i saw on the guide does not list an I9020XXJK8..unless the remaining characters after i9020 are supposed to equal one of the I9020a/I9020t/I9023 versions....
My phone's information:
Click to expand...
Click to collapse
Didn't have Nv.Log? Ohhhhh crap lol
Sent From In between Your Moms Boobies
i presume not having that file poses a problem for my phone
headsh0tshurt said:
i presume not having that file poses a problem for my phone
Click to expand...
Click to collapse
I think it does because u need all three ... =/ maybe I can upload mine later? Or pm me and ill send it via email?
Sent From In between Your Moms Boobies
thx. i'll send you a pm now
did the missing file fix the issue?
no it did not. i tried flashing the radio for my i9020xxjk8 from the xda site. it began to install but then it said installation aborted...there was no reason given as to why it did that. but my phone still works normally and the wifi is still not working
i woke up this morning and my phone was stuck in a boot loop. removed the battery 3 times with no success. i also tried a restore of the boot from a backup but it said it couldnt find the system.cache.img and failed. i then just booted it into recovery mode and installed the older OS version (2.3.6) and i was able to get back into the phone. however the phone is now seen as being unrooted so i have to re-root the device so i can properly run cm7.
---------- Post added at 09:23 AM ---------- Previous post was at 09:21 AM ----------
Here is the link for the thread w/ the 2.3.6 version for the i9020t that i have -- http://forum.xda-developers.com/showthread.php?t=1063664
also i downloaded the Android 2.3.6/GRK39F/XXKF1 Radio/KA3 Bootloader
what phone are you using?
i'm using the tmobile nexus s
im sending mine back to samsung for a repair.
long story short I havent used this phone for months and I just sold it and once I updated the phone it said no service so I did research and tried updating my radio but I keep getting signature verification failed... Whats the matter?
2.3.6
bb: NO DGSXXF1
build:grk39f
kernel v: 2.6.35.7.gf5f63ef [email protected] #1
What am I doing wrong? I would like to ship the phone out today
can somebody please tell me how to return the phone to the stock version that radios work!!!! man this is driving me crazy I just wiped everything off my phone now I think I gotta root it again
Seems like you flashed a bad image, the obvious solution would to be dig deeper on the image you flashed to find something more up to date.
Sent from my Nexus S using XDA App
n023b said:
long story short I havent used this phone for months and I just sold it and once I updated the phone it said no service so I did research and tried updating my radio but I keep getting signature verification failed... Whats the matter?
2.3.6
bb: NO DGSXXF1
build:grk39f
kernel v: 2.6.35.7.gf5f63ef [email protected] #1
What am I doing wrong? I would like to ship the phone out today
Click to expand...
Click to collapse
I'd download the full ROM version of the latest firmware (available in this forum) and re-flash from recovery, probably worth wiping system/data/cache etc via recovery first.
The full ROM will include the latest radio image for your handset along with everything else it needs.
Best of luck.
Most radio problems can be fixed by restoring an EFS backup.
Flash the latest stock from and radios via fast boot.
Sent from my Nexus S 4G using xda premium
No need... Ull need root explorer and a radio that your phone works with.
Flash the radio first ( no service still)
Then go into root explorer and your going to go.into efs file and move the following files to root of SD
Nv.log
Nv_Data.bin
Nv_Data.bin.md5
Once u do that... restart your phone and u will be fine.
Note the once u move the files into SD Card... the files will automatically be in efs file again and remain in SD Card as well
-Google
iGoogleNexus said:
No need... Ull need root explorer and a radio that your phone works with.
Flash the radio first ( no service still)
Then go into root explorer and your going to go.into efs file and move the following files to root of SD
Nv.log
Nv_Data.bin
Nv_Data.bin.md5
Once u do that... restart your phone and u will be fine.
Note the once u move the files into SD Card... the files will automatically be in efs file again and remain in SD Card as well
-Google
Click to expand...
Click to collapse
Did this the other day forgot to tell you guys it worked. Thank you!
Hi Everyone
Got myself in a bit of a situation, Went to install the latest Helly Bean Rom Downloaded the file with the big button and put it on my external sd card, followed the step by step untill...
Install instructions:
coming from any other rom:
- make sure to have gingerbread bootloaders
- wipe data/factory reset
- flash allinone.zip
- reboot recovery
- flash allinone.zip again
- flash Helly_Bean_AddOn or Helly_Bean inverted AddOn ......here when i realized i hadn't got the file furthermore the file i have is named
helly_bean_initial.zip I couldn't find the other file and now my phone just bootloops.
Please give help me get the phone working again I don't know what to do and im panicking.
I9000NB said:
I couldn't find the other file and now my phone just bootloops.
Please give help me get the phone working again I don't know what to do and im panicking.
Click to expand...
Click to collapse
Download the files needed to your PC, than use CWM to copy them to your Phone in USB mounts and Storage , after that flash
xsenman said:
Download the files needed to your PC, than use CWM to copy them to your Phone in USB mounts and Storage , after that flash
Click to expand...
Click to collapse
Thankyou xsenman that sounds simple enough,:fingers-crossed:
Well that worked great its now installed and the new rom looks sweet.
Problem i have now is im getting "An invalid IMEI number could cause network issues including the inability to call" anyone seen this before ?
Just found this :
Everyone is having IMEI problems, here is how you fix it.
1) Get ES file explorer or root explorer
2)Look in sdcard/backup/efs
3)Copy nv_data.bin, nv_data.bin.md5 and nv.log to /efs.
4) Reboot and enjoy!
Ill post back after gym if it works =D
That should work. Actually a friend of mine had similar issue with his phone but from what I know this solution helped him to get rid of the problem
Typed with my I9001
tryed the above fix with astro manager from recovery and after file copy and reboot i still get imei error.
thanks for the post ruthlessrat, its good to know someone else has tried the above fix and its worked for them maybe others who stuble across this thread may be able to use it although i can confirm it did not work for me.
I'm assuming my nv_data.bin, nv_data.bin.md5 and nv.log were bad, I'm looking into a imei fix here
http://forum.xda-developers.com/showthread.php?t=881162 Hopefully this will resolve the last issue.
Edit: Good news I've got another phone to cover me for a while so I can work on getting this phone set up
how i want it, I think i may need to return to a stock rom, will this restore the imei ?
Edit2 : Reinstalled Gapps from thread : http://forum.xda-developers.com/showthread.php?t=1796675 this time its worked and Google play is now working fully so ive installed titanium backup and a few other applications that may come in use.
In the meantime alternate imei fixes and any advice would be useful on other cool features / functionality unique to JB. Thankyou to everyone again without the assistance it would have taken me allot further to get to this point.
I9000NB said:
In the meantime alternate imei fixes and any advice would be useful
Click to expand...
Click to collapse
Need a Solution, My Android Solutions
xsenman said:
Need a Solution, My Android Solutions
Click to expand...
Click to collapse
Funny you should suggest that ive come across your thread, thanked, rated 5 and believe it should be newsworthy that thread could turn into a real noob's guide, I like it very much. I tried the first suggestion of copying the files , afraid it didn't work.
Second to that i tried this :http://www.youtube.com/watch?feature=player_embedded&v=JqLK_2I-SBM
but unfortunately my nv_data.bin is pure "FF" in the hex editor so I assume this is some kind of default setting? anyone know ?
I am now going to try..
you can start from the beginning.. go back to GB 2.36 (use a JVU ROM + Root, upgrade to ICS CM 9 and than to CM10
Solution for i9000 on JB:-Try not to jump from Gingerbread to Jellybean, as all upgrades should be done progressively. meaning you need to be on a GB 2.3.6> than into ICS and finally into JB.
I'm going to use GB 2.3.6 from sammobile.com
Can anyone recommend an ICS rom ?
following this I will flash Helly Bean latest nightly again.
Edit: Well Ive flashed back to 2.3.6 JVU & used the JVU CF - Root which works great, Ive backed up my rom and ets folder ready for jellybean the problem is when running through the installation ui it gets stuck on the final " Helly Bean installed" screen after making your software selections,
When I click next to finish it just hangs and the phone becomes completely unresponsive. at this point Ive removed battery and restarted but alas I'm still on cf rooted gingerbread. I don't understand why as it worked fine before.
Ive tried clearing both cache's and reset, this made no difference.
Ive also reinstalled stock rom, re flashed CF-Root & Tried again with no success.
I'm going to look into ICS roms and post back.
I9000NB said:
Solution for i9000 on JB:-Try not to jump from Gingerbread to Jellybean, as all upgrades should be done progressively. meaning you need to be on a GB 2.3.6> than into ICS and finally into JB.
Click to expand...
Click to collapse
try CM 9 first than on to JB or HB or any other Bean
xsenman said:
try CM 9 first than on to JB or HB or any other Bean
Click to expand...
Click to collapse
Okay been having a few issues installing CM 9 so i have installed CM 7 for the moment,
Trying to fix CM9 atm keep getting "installation aborted (Bad)"
Fixed/Update : Move files to internal storage, Installed latest CM9, Downloading CM10 Nightly
Update 2 : CM10 Nightly installed works great & GAPPS latest version from goo.im.
Thanks again xsenman without you this would have been allot longer process, I really appreciate it !
Thread End.
Background:
My 2 months old LG Nexus4 (with updated 4.3 OTA) suddenly stopped working a week back and wont boot again. It was stuck in a boot-loop. I tried flashing the 4.3 image again by using cwp recovery and it made my phone work again. Though the boot times were unpredictable. I was also able to connect to the network only intermittently.
So I downgraded to factory 4.2 with factory boot, recovery, radio and everything else. Phone was working fine with quick boot up times. The only problem was it was not connecting to any network.
Tried with custom radio .33/.84 radio image. .27 radio image as well as the stock radio for 4.2. But no luck.
The details of all this are at : http://forum.xda-developers.com/showthread.php?t=2451594
The current status of the phone is :
Service State : out of service.
IMEI : Unknown.
IMEI SV : Unknown.
Baseband version : Unknown.
Tried toggling the Flight mode but no use.
Whats wrong here ?
kaustubhpatil said:
Service State : out of service.
IMEI : Unknown.
IMEI SV : Unknown.
Baseband version : Unknown.
Click to expand...
Click to collapse
Some carriers will not let you connect if your IMEI has been tampered with in your phone.
You have to find a way to get your IMEI back. I know how to do this for my Optimus 2X, but have no idea for the nexus...
I was reading your other thread which I honestly think you should of changed the heading a little since there was history there and information that people may need to help you solve this problem. Now which version of TWRP did you flash since that was causing an issue with network connections for some.
Also as a suggestion the backup you made per suggestion from Simms in the other thread please backup to your harddrive. After doing so I would either follow the steps here. I think your best bet is too start over again and go back to a factory image
Couple of other guides and questions like yours.
http://forum.xda-developers.com/showthread.php?t=2453364
http://forum.xda-developers.com/showthread.php?t=1995688
Hi Playya,
I had flashed openrecovery-twrp-2.6.3.0-mako.img .
And yes.. I need to change the name of the other thread.
i think starting over again might help as well, flash the factory img via fastboot, the 4.3 img. if it doesnt work, there is a lost my imei thread here in the forums(ill look for it too).
yes.. I tried flashing 4.3 again (the second time). Along with all the factory images. But when I do that the boot-loop problem happens. So I again downgraded to 4.2.
In my other thread I had put in the logs that said :
"cant partition non-vfat: datamedia
cant format unknown volume: /external_sd
cant format unknown voume: /emmc"
Is this some kinda releated to the IMEI issue ?
kaustubhpatil said:
yes.. I tried flashing 4.3 again (the second time). Along with all the factory images. But when I do that the boot-loop problem happens. So I again downgraded to 4.2.
In my other thread I had put in the logs that said :
"cant partition non-vfat: datamedia
cant format unknown volume: /external_sd
cant format unknown voume: /emmc"
Is this some kinda releated to the IMEI issue ?
Click to expand...
Click to collapse
tell me, is a rma possible? it sounds like something might have corrupted, in your phones partitions..
simms22 said:
tell me, is a rma possible? it sounds like something might have corrupted, in your phones partitions..
Click to expand...
Click to collapse
If I understand you correctly you mean returning / exchanging the phone. Dont know.. A friend bought this for me from US and I am in India. Even if its possible it will be a pretty lengthy process...
Hi everyone,
I have tried lot of things.. but still not able to get around this problem
one more thing : I can see the baseband version as M9615A-CEFWMAZM-2.0.1700.48 in the bootloader mode. But when I boot in normal mode the baseband is unknown
kaustubhpatil said:
one more thing : I can see the baseband version as M9615A-CEFWMAZM-2.0.1700.48 in the bootloader mode. But when I boot in normal mode the baseband is unknown
Click to expand...
Click to collapse
Did you find a solution for your problem?
venec said:
Did you find a solution for your problem?
Click to expand...
Click to collapse
Not yet.. tried many radio images. All of them show up in bootloader but not when the actual OS boots up. In the phone setting it still shows baseband, imei unknown..
kaustubhpatil said:
Not yet.. tried many radio images. All of them show up in bootloader but not when the actual OS boots up. In the phone setting it still shows baseband, imei unknown..
Click to expand...
Click to collapse
Do this. Your partitions are messed up I think. This happened to mine, and that guide fixed it.
lopezk38 said:
Do this. Your partitions are messed up I think. This happened to mine, and that guide fixed it.
Click to expand...
Click to collapse
Thanks. I looked at that thread. It is too long and I was not able to exactly understand what is being done there. Could you in short explain what they are trying to do there ? I am sorry, I am a complete novice in Android, so this might be a stupid question..
lopezk38 said:
Do this. Your partitions are messed up I think. This happened to mine, and that guide fixed it.
Click to expand...
Click to collapse
Already tried that multiple times, still no luck
lopezk38 said:
Do this. Your partitions are messed up I think. This happened to mine, and that guide fixed it.
Click to expand...
Click to collapse
The instructions on that page seem to be for the 8GB Nexus4. Mine is 16GB. would those work on my phone ?
kaustubhpatil said:
The instructions on that page seem to be for the 8GB Nexus4. Mine is 16GB. would those work on my phone ?
Click to expand...
Click to collapse
There are a few extra steps for 16 GB phones. You just have to scroll down a bit. My phone is a 16 GB, and it all turned out fine
lopezk38 said:
There are a few extra steps for 16 GB phones. You just have to scroll down a bit. My phone is a 16 GB, and it all turned out fine
Click to expand...
Click to collapse
Hi,
Did the problem get solved? I am facing the same problem on my nexus4, 8GB after I accidentally flashed my phone. Don't really know how to fix it.